git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: dloewenherz@gmail.com, git@vger.kernel.org
Subject: Re: Pretty date option for git tag?
Date: Mon, 18 May 2009 10:20:49 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0905181015080.3301@localhost.localdomain> (raw)
In-Reply-To: <4A118696.80902@drmicha.warpmail.net>



On Mon, 18 May 2009, Michael J Gruber wrote:
> 
> You might want to experiment with
> 
> git log --tags --simplify-by-decoration --pretty="format:%ai %s"
> 
> which may show a few more commits than just the tags but comes close to
> the output you envisage.

Ooh, evil. I like it.

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).

As you mention, "--simplify-by-decoration" will show merges too (unless it 
can linearize the tag history), but you can work around that by making the 
format be "format:%ai %d" where that '%d' shows the decoration of the 
commit, rather than the commit summary. Now the merges that aren't tagged 
stand out very clearly.

Of course, the above will just work for commit tags. If you've tagged a 
tree or a blob, the above gives you bubkis.

			Linus

  reply	other threads:[~2009-05-18 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 15:14 Pretty date option for git tag? dloewenherz
2009-05-18 16:02 ` Michael J Gruber
2009-05-18 17:20   ` Linus Torvalds [this message]
2009-05-18 17:45     ` Jeff King
2009-05-18 17:58       ` [PATCH] for-each-ref: fix segfault in copy_email Jeff King
2009-05-18 21:11       ` Pretty date option for git tag? Thomas Rast
2009-05-18 21:27         ` Jeff King

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=alpine.LFD.2.01.0905181015080.3301@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=dloewenherz@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.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 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).