git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Umali <rickumali@gmail.com>
To: Carsten Mattner <carstenmattner@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: tag scheme
Date: Wed, 26 Nov 2014 16:13:57 -0500	[thread overview]
Message-ID: <20141126211356.GA15127@rick-t60> (raw)
In-Reply-To: <20141125170941.GA23258@peff.net>

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

      reply	other threads:[~2014-11-26 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 16:17 tag scheme Carsten Mattner
2014-11-25 17:09 ` Jeff King
2014-11-26 21:13   ` Rick Umali [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141126211356.GA15127@rick-t60 \
    --to=rickumali@gmail.com \
    --cc=carstenmattner@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).