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

Re: Pretty date option for git tag?

From
Jeff King <peff@peff.net>
Date
May 18, 2009, 17:45 UTC
Message-ID
<20090518174547.GA14509@sigill.intra.peff.net>
In-Reply-To
<alpine.LFD.2.01.0905181015080.3301@localhost.localdomain>
On Mon, May 18, 2009 at 10:20:49AM -0700, Linus Torvalds wrote:
> It's a rather expensive operation, but it does have the really nice 
> property that it will show the date of the commit the tag is pointing to, 
> rather than necessarily the date of the tag itself (which is not 
> well-defined unless the tag is signed).

It seems like you should be able to script around for-each-ref and remain efficient, but I don't think there is a way to convince it to dereference tags. Something like:

  git for-each-ref --format='%(refname)
  Tag: %(taggername) %(taggeremail) %(taggerdate)
  Commit: %(authorname) %(authoremail) %(authordate)
  ' refs/tags

almost works, but the commit fields are always empty. So I think you would have to parse and manually rev-parse each one.

-Peff
PS The for-each-ref command above caused a segfault when run in git.git.
   Patch to follow.
Previous: Linus TorvaldsNext: Jeff King
Message 4 of 7 in “Pretty date option for git tag?”
  1. dloewenherz@gmail.comMay 18, 2009
  2. Michael J GruberMay 18, 2009
  3. Linus TorvaldsMay 18, 2009
  4. Jeff KingMay 18, 2009
  5. for-each-ref: fix segfault in copy_emailJeff King, May 18, 2009
  6. Thomas RastMay 18, 2009
  7. Jeff KingMay 18, 2009

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.