From: Michael J Gruber <git@drmicha.warpmail.net>
To: dloewenherz@gmail.com, git@vger.kernel.org
Subject: Re: Pretty date option for git tag?
Date: Mon, 18 May 2009 18:02:30 +0200 [thread overview]
Message-ID: <4A118696.80902@drmicha.warpmail.net> (raw)
In-Reply-To: <20090518151440.GA10536@andros.its.yale.edu>
dloewenherz@gmail.com venit, vidit, dixit 18.05.2009 17:14:
> It is relatively hard to verify the date a tag was created unless it was been
> gpg/pgp-signed at the time of creation, no? I suppose that the Unix timestamp
> included in each tag file is useful for sorting, but it's not very easy for
> people to digest. Additionally, we have our `log.date` config, why not use it
> here for some sort of option, like `--pretty=date` to make it easy to see when
> a tag was created?
>
> I.e.
>
> $ git tag -l --pretty=date
> ...
> Mon, 13 Apr 2009 00:06:25: v1.6.3-rc0
> Sat, 18 Apr 2009 22:11:00: v1.6.3-rc1
> Sat, 25 Apr 2009 06:01:13: v1.6.3-rc2
> Sun, 26 Apr 2009 23:43:48: v1.6.3-rc3
> Sat, 02 May 2009 06:32:21: v1.6.3-rc4
> Wed, 13 May 2009 05:30:37: v1.6.3.1
>
> I don't know if this is feasible. Perhaps there already exists a feature for
> this that I'm unaware of. Or maybe this would be a waste of time.
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.
Michael
next prev parent reply other threads:[~2009-05-18 16:02 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 [this message]
2009-05-18 17:20 ` Linus Torvalds
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=4A118696.80902@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=dloewenherz@gmail.com \
--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).