Hi, 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). This seems like a worse situation to me, as there's no way to tell which branch they were built from. I feel that this inconsistency is confusing, though I admit that anyone using the devel repo should be competent enough to know what branch they're checking out. Still, would it be possible to bring the tags up to date, so that versions are consistent? Thanks, WorMzy Tykashi [1] http://repo.or.cz/r/btrfs-progs-unstable/devel.git [2] https://github.com/kdave/btrfs-progs -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
