On Wed, Dec 11, 2013 at 03:59:48PM +0000, WorMzy Tykashi wrote: > It's not a big deal, but I've just noticed that the most recent > unstable-integration btrfs tools (built from [1]) are still reporting > their version as v0.20-rc1-638-g8e44385, rather than > v3.12-xxx-xxxxxxxx. I believe this is because the master branch in the > devel repository has not been tagged with the new version. > > The github clone/mirror(?) of the devel repository [2] has no tags for > some reason, and the btrfs tools built from it report their version > simply as v0.20-rc1 or v3.12 (depending on which branch you check > out). Sorry, I haven't pushed the tags, fixed now. The repos are mostly identical to increase availability. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
