2009/3/19 Jeff King <peff@xxxxxxxx>: > 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@xxxxxxxxxxx> 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/" -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
