All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre tags
Date: Wed, 24 Nov 2010 14:17:53 -0800	[thread overview]
Message-ID: <4CED8F11.8090606@llnl.gov> (raw)
In-Reply-To: <A76D5D7F-5FFD-4802-B298-2CAFCC0E9F98@oracle.com>

On 11/24/2010 12:30 PM, Andreas Dilger wrote:

> What specific use do you have for the tags, and is the above tag hash-to-commit-date mapping enough?  Is there any reason NOT to always use "-a" when creating a tag?

I hadn't done a fetch from prime in a couple of weeks, and when I just 
did it I saw that v1_8_5_RC4 had been tagged 1.8.5.  In that case, you 
can see that the change to lustre-version.ac to make it 1.8.5 actually 
happened several commits before the actual 1.8.5 tag.  I have no way of 
knowing how long v1_8_5_RC4 was in existence before it became 1.8.5.

Not a big deal, really.  But it would have been simple to see what 
happened if the tag had been of the annotated/signed type.

Also, in the past "git describe" did not stop at lightweight tags, only 
at annotated/signed tags.  That may have changed in newer versions of git.

I believe that annotated tags for lustre version numbers.

In fact, it kind of seems like annotated tags should be the default 
behavior for "git tag".  I can't think of a good reason why you would 
not want a tag to be annotated if you are going to share it with others.

My guess is that lightweight tags are just the default in git for 
historical reasons (they were implemented first).

Chris

  reply	other threads:[~2010-11-24 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 19:25 [Lustre-devel] Lustre tags Christopher J. Morrone
2010-11-24 20:30 ` Andreas Dilger
2010-11-24 22:17   ` Christopher J. Morrone [this message]
2010-11-25  4:17     ` Brian J. Murrell

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=4CED8F11.8090606@llnl.gov \
    --to=morrone2@llnl.gov \
    --cc=lustre-devel@lists.lustre.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.