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

Re: Pretty date option for git tag?

From
Thomas Rast <trast@student.ethz.ch>
Date
May 18, 2009, 21:11 UTC
Message-ID
<200905182311.41876.trast@student.ethz.ch>
In-Reply-To
<20090518174547.GA14509@sigill.intra.peff.net>
Jeff King wrote:
> 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.
Actually there's the * operator.  For example
  git$ git for-each-ref --format="%(objecttype) %(*objecttype)" refs/tags/v1.6.0
  tag commit
Does that solve the problem at hand?
-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Jeff KingNext: Jeff King
Message 6 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.