Re: What's in git.git (part #2)

From: Junio C Hamano <junkio@cox.net>
Date: Jun 2, 2006, 06:40 UTC
Message-ID: <7v3beodpqs.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060602023545.GA5039@spearce.org>

Shawn Pearce <spearce@spearce.org> writes:

> I find it useful to track what I've sent to you just in case I
> screw up some ref somewhere.  I like knowing that if I perform a
> bad update-ref call (which I'm prone to do sometimes) that I can
> recover quickly as the log exists.

I find it interesting to be able to say:

	$ git log next@{yesterday}..next

I often find myself getting curious to see:

	$ git reflog next
        Wed May 31 14:23:58 2006 -0700
                62b693a... Merge branch 'master' into next
        Wed May 31 14:26:39 2006 -0700
                422dfaf... Merge branch 'lt/tree-2' into next
        Wed May 31 15:14:58 2006 -0700
                100c25f... Merge branch 'ff/svnimport' into next
        Wed May 31 15:23:54 2006 -0700
                a25963b... Merge branch 'jc/fmt-patch' into next
        ...

The latter is probably not so useful in practice -- I suspect that I would want to see such a list only while I am interested in how well reflog works.