linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* btrfs-progs integration branch versioning
@ 2013-12-11 15:59 WorMzy Tykashi
  2013-12-11 16:37 ` David Sterba
  0 siblings, 1 reply; 3+ messages in thread
From: WorMzy Tykashi @ 2013-12-11 15:59 UTC (permalink / raw)
  To: linux-btrfs

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: btrfs-progs integration branch versioning
  2013-12-11 15:59 btrfs-progs integration branch versioning WorMzy Tykashi
@ 2013-12-11 16:37 ` David Sterba
  2013-12-11 17:29   ` WorMzy Tykashi
  0 siblings, 1 reply; 3+ messages in thread
From: David Sterba @ 2013-12-11 16:37 UTC (permalink / raw)
  To: WorMzy Tykashi; +Cc: linux-btrfs

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: btrfs-progs integration branch versioning
  2013-12-11 16:37 ` David Sterba
@ 2013-12-11 17:29   ` WorMzy Tykashi
  0 siblings, 0 replies; 3+ messages in thread
From: WorMzy Tykashi @ 2013-12-11 17:29 UTC (permalink / raw)
  To: dsterba, WorMzy Tykashi, linux-btrfs

On 11 December 2013 16:37, David Sterba <dsterba@suse.cz> wrote:
>
> Sorry, I haven't pushed the tags, fixed now. The repos are mostly
> identical to increase availability.
>
> david

Cheers for that.


WorMzy

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-12-11 17:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-11 15:59 btrfs-progs integration branch versioning WorMzy Tykashi
2013-12-11 16:37 ` David Sterba
2013-12-11 17:29   ` WorMzy Tykashi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).