git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* tag scheme
@ 2014-11-25 16:17 Carsten Mattner
  2014-11-25 17:09 ` Jeff King
  0 siblings, 1 reply; 3+ messages in thread
From: Carsten Mattner @ 2014-11-25 16:17 UTC (permalink / raw)
  To: git

I'm looking for advice on a tagging scheme, especially pros/cons
of using a 'v' prefix as in v2.1.0 like git does.

My impression is that using a common prefix for tags makes it
simple to distinguish from maintenance branches for past releases
but it seems that most repositories use tags without a prefix.
Before I settle on using vX.Y.Z (which I favor right now), I'd like to
understand why some projects do not prefix tags.

Any comments?

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

* Re: tag scheme
  2014-11-25 16:17 tag scheme Carsten Mattner
@ 2014-11-25 17:09 ` Jeff King
  2014-11-26 21:13   ` Rick Umali
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff King @ 2014-11-25 17:09 UTC (permalink / raw)
  To: Carsten Mattner; +Cc: git

On Tue, Nov 25, 2014 at 05:17:52PM +0100, Carsten Mattner wrote:

> I'm looking for advice on a tagging scheme, especially pros/cons
> of using a 'v' prefix as in v2.1.0 like git does.
> 
> My impression is that using a common prefix for tags makes it
> simple to distinguish from maintenance branches for past releases
> but it seems that most repositories use tags without a prefix.
> Before I settle on using vX.Y.Z (which I favor right now), I'd like to
> understand why some projects do not prefix tags.

I cannot speak definitely for people who prefer no prefix, but I imagine
that they simply see it as useless noise.

Personally, I like the prefix because it lets me wildcard-match only the
releases (and not other random tags I might have):

  git tag -l 'v*'

Of course I quite often want to drop release-candidate tags from such a
list, too, and I have to resort to "grep -v -- -rc" to do so. :)

-Peff

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

* Re: tag scheme
  2014-11-25 17:09 ` Jeff King
@ 2014-11-26 21:13   ` Rick Umali
  0 siblings, 0 replies; 3+ messages in thread
From: Rick Umali @ 2014-11-26 21:13 UTC (permalink / raw)
  To: Carsten Mattner; +Cc: Jeff King, git

On Tue, Nov 25, 2014 at 12:09:42PM -0500, Jeff King wrote:
> On Tue, Nov 25, 2014 at 05:17:52PM +0100, Carsten Mattner wrote:
> > I'm looking for advice on a tagging scheme, especially pros/cons
> > of using a 'v' prefix as in v2.1.0 like git does.
> > 
> > My impression is that using a common prefix for tags makes it
> > simple to distinguish from maintenance branches for past releases
> > but it seems that most repositories use tags without a prefix.
> > Before I settle on using vX.Y.Z (which I favor right now), I'd like to
> > understand why some projects do not prefix tags.
> 
> I cannot speak definitely for people who prefer no prefix, but I imagine
> that they simply see it as useless noise.
> 
> Personally, I like the prefix because it lets me wildcard-match only the
> releases (and not other random tags I might have):
> 
>   git tag -l 'v*'
> 
> Of course I quite often want to drop release-candidate tags from such a
> list, too, and I have to resort to "grep -v -- -rc" to do so. :)

I wanted to second the prefix notation. I have a repository with 
three tag prefixes (namespaces?): SUBMIT, CODE and V. The prefix 
helps me stay organized. I've been adding -n to the git tag command
that Jeff mentioned:

git tag -l -n 'SUBMIT*'
-- 
Rick (www.manning.com/umali) Umali

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

end of thread, other threads:[~2014-11-26 21:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-25 16:17 tag scheme Carsten Mattner
2014-11-25 17:09 ` Jeff King
2014-11-26 21:13   ` Rick Umali

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).