git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 5/5] describe: Break annotated tag ties by tagger date

From
Andreas Ericsson <ae@op5.se>
Date
Apr 13, 2010, 09:27 UTC
Message-ID
<4BC43902.2040903@op5.se>
In-Reply-To
<1271114729-18166-5-git-send-email-spearce@spearce.org>
On 04/13/2010 01:25 AM, Shawn O. Pearce wrote:
Show 7 quoted lines
> If more than one annotated tag points at the same commit, use the
> tag whose tagger field has a more recent date stamp.  This resolves
> non-deterministic cases where the maintainer has done:
> 
>    $ git tag -a -m "2.1-rc1" v2.1-rc1  deadbeef
>    $ git tag -a -m "2.1"     v2.1      deadbeef
>

We use this patch-series in our buildsystem, where we just now tagged about 14 projects as stable (on top of an earlier beta tag). Everything's working just fine, so...

Tested-By: Andreas Ericsson <ae@op5.se>
Thanks a lot, Shawn.
-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
Previous: Shawn O. PearceNext: Thomas Rast
Message 13 of 17 in “git describe bug?”
  1. Dustin SallingsApr 2, 2010
  2. Shawn O. PearceApr 2, 2010
  3. Andreas EricssonApr 6, 2010
  4. Shawn O. PearceApr 11, 2010
  5. describe: Break annotated tag ties by tagger dateShawn O. Pearce, Apr 11, 2010
  6. Junio C HamanoApr 11, 2010
  7. Shawn O. PearceApr 11, 2010
  8. 1/5 tag.c: Correct indentationShawn O. Pearce, Apr 12, 2010
  9. 2/5 tag.h: Remove unused signature fieldShawn O. Pearce, Apr 12, 2010
  10. 3/5 tag.c: Refactor parse_tag_buffer to be saner to programShawn O. Pearce, Apr 12, 2010
  11. 4/5 tag.c: Parse tagger date (if present)Shawn O. Pearce, Apr 12, 2010
  12. 5/5 describe: Break annotated tag ties by tagger dateShawn O. Pearce, Apr 12, 2010
  13. Andreas EricssonApr 13, 2010
  14. Thomas RastApr 13, 2010
  15. Shawn O. PearceApr 13, 2010
  16. Junio C HamanoApr 13, 2010
  17. Shawn O. PearceApr 13, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.