Re: a few remaining issues...

From: Junio C Hamano <junkio@cox.net>
Date: Jan 9, 2007, 20:22 UTC
Message-ID: <7vtzz0j6hf.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0701091218080.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 8 quoted lines

> On Fri, 5 Jan 2007, Shawn O. Pearce wrote:
>
>> I myself am also severly lacking in time right now.
>
> Did you have any chance to look at the patch I posted? It adds 
> "--walk-reflogs" option to the revision walker, and as long as there is 
> reflog information, traverses the commits in that order. It also shows the 
> reflog data just below the "commit" line.

What does it do when you say, for example:

	git log --walk-reflogs master..next

I couldn't make heads or tails out of the patch and did not understand what it was trying to do. It looked as if you were making the log traversal machinery to walk _both_ reflog (probably from the latest to older) and the usual ancestry.