From: Jeff King <peff@peff.net>
Date: Thu, 09 Sep 2010 19:51:59 GMT
Subject: Re: git log over restricts output when using --follow?
Message-ID: <20100909195159.GC1146@sigill.intra.peff.net>
In-Reply-To: <4C86D5AE.6030302@verizon.net>

On Tue, Sep 07, 2010 at 08:15:42PM -0400, Gregg Leichtman wrote:

> (3)
> 
> |gsl@aragorn:~/gitTest> gitnp log -2 --follow --pretty=oneline junk.txt
> 500e8791578c5baf7a139d4997841769a995ac6b mod of junk and junk3
> |
> 
> (4)
> 
> |gsl@aragorn:~/gitTest> gitnp log -2 --pretty=oneline junk.txt
> 500e8791578c5baf7a139d4997841769a995ac6b mod of junk and junk3
> 594ceed7a0fb35a860a6e2cb913d5398f09a861f 1st mod junk.txt
> |
> 
> Why don't I see 2 output lines for item (3) above?

Without looking closer into the problem, I would guess that it is
because of the hack-ish way that --follow is implemented. That is,
most history pruning and simplification happens outside of the actual
--follow traversal. So yes, it looks like a defect, but fixing it may
involve rewriting --follow entirely.

But don't let that discourage you from looking further. :)

-Peff