From: demerphq <demerphq@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Jeff King <peff@peff.net>, Git <git@vger.kernel.org>
Subject: Re: Gnome chose Git
Date: Thu, 19 Mar 2009 22:48:51 +0100 [thread overview]
Message-ID: <9b18b3110903191448x4cd62306idae9ce70630a389d@mail.gmail.com> (raw)
In-Reply-To: <20090319214317.GU23521@spearce.org>
2009/3/19 Shawn O. Pearce <spearce@spearce.org>:
> demerphq <demerphq@gmail.com> wrote:
>> Outside of parsing the reflog directly, (which feels wrong and dirty
>> to me), how does one find out the times that a reflog entry was
>> created?
>>
>> The closest thing i could find was git log -g, but that shows the time
>
> git reflog -g branch@{now}
>
> the @{now} suffix is the magic to make it show the time.
Ah cool. Its not documented but that at least would have sorted my
immediate needs.
But for a logging tool it would be nice to get something like:
2009-03-19 21:46 > de9b652... HEAD@{0}: commit: pod/perlreftut.pod:
keep example in tune with the times
2009-03-19 21:44 > 53102b2... HEAD@{1}: HEAD^: updating HEAD
2009-03-19 21:40 > a9a8f59... HEAD@{2}: commit: must stay contemporary
instead of:
$ git reflog -g HEAD@{now}
de9b652... HEAD@{57 minutes ago}: commit: pod/perlreftut.pod: keep
example in tune with the times
53102b2... HEAD@{61 minutes ago}: HEAD^: updating HEAD
a9a8f59... HEAD@{61 minutes ago}: commit: must stay contemporary
But thanks a lot for the info. I take this is documented in a newer
release than i currently have?
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2009-03-19 21:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 11:23 Gnome chose Git Teemu Likonen
2009-03-19 11:29 ` Sverre Rabbelier
2009-03-19 11:33 ` Mike Ralphson
2009-03-19 16:29 ` Andreas Ericsson
2009-03-19 13:33 ` Michael J Gruber
[not found] ` <1cd1989b0903190643p19a40718yc4fd2730aab0a9a0@mail.gmail.com>
[not found] ` <49C24D9B.1060301@drmicha.warpmail.net>
2009-03-19 14:01 ` Pat Notz
2009-03-19 15:16 ` Shawn O. Pearce
2009-03-19 15:50 ` Pat Notz
2009-03-19 20:14 ` Jeff King
2009-03-19 21:40 ` demerphq
2009-03-19 21:43 ` Shawn O. Pearce
2009-03-19 21:44 ` Shawn O. Pearce
2009-03-19 21:51 ` demerphq
2009-03-19 21:53 ` Shawn O. Pearce
2009-03-19 21:59 ` demerphq
2009-03-19 23:17 ` Johannes Schindelin
2009-03-19 21:48 ` demerphq [this message]
2009-03-20 5:28 ` Jeff King
2009-03-20 6:00 ` [PATCH] make oneline reflog dates more consistent with multiline format Jeff King
2009-03-20 8:33 ` Gnome chose Git Michael J Gruber
2009-03-20 20:03 ` 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=9b18b3110903191448x4cd62306idae9ce70630a389d@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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).