From: "Shawn O. Pearce" <spearce@spearce.org>
To: demerphq <demerphq@gmail.com>
Cc: Jeff King <peff@peff.net>, Git <git@vger.kernel.org>
Subject: Re: Gnome chose Git
Date: Thu, 19 Mar 2009 14:44:32 -0700 [thread overview]
Message-ID: <20090319214432.GV23521@spearce.org> (raw)
In-Reply-To: <20090319214317.GU23521@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> wrote:
> 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}
Arrgh, I of course actually meant
git log -g branch@{now}
> the @{now} suffix is the magic to make it show the time.
--
Shawn.
next prev parent reply other threads:[~2009-03-19 21:46 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 [this message]
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
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=20090319214432.GV23521@spearce.org \
--to=spearce@spearce.org \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).