git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: demerphq <demerphq@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git <git@vger.kernel.org>
Subject: Re: Gnome chose Git
Date: Thu, 19 Mar 2009 22:40:39 +0100	[thread overview]
Message-ID: <9b18b3110903191440w20ca9801pfb218cc4b10ea769@mail.gmail.com> (raw)
In-Reply-To: <20090319201405.GD17028@coredump.intra.peff.net>

2009/3/19 Jeff King <peff@peff.net>:
> On Thu, Mar 19, 2009 at 09:50:39AM -0600, Pat Notz wrote:
>
>> On Thu, Mar 19, 2009 at 9:16 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
>> >
>> > Why are people reinventing the reflog, and core.logallrefupdates ?
>> >
>>
>> Hmmm, lack of awareness of core.logallrefupdates in my case.  Thanks
>> for the pointer.
>
> But do note that reflogs expire eventually, so you will want to also
> look at gc.reflogexpire and gc.reflogexpireunreachable if you want to
> keep this as an activity log forever.

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
of the commit that was switched to, not the time the reflog entry was
created. I dont see a --format pattern for it, and there doesnt seem
to be a switch to git reflog to do it. (I had initially (before
RTFM'ing) assumed that git reflog -v would show the times, but
apparently not).

If the times were easy to access then it would be much more useful as
a general logging facility.

cheers,
Yves




-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

  reply	other threads:[~2009-03-19 21:42 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 [this message]
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
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=9b18b3110903191440w20ca9801pfb218cc4b10ea769@mail.gmail.com \
    --to=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).