From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Sat, 01 Mar 2008 02:35:54 GMT
Subject: Anomaly in git log?
Message-ID: <20080301133554.7a3cbd35.sfr@canb.auug.org.au>

Hi,

I noticed that under some circumstances "git log <range> -- <file>" will
not show you all the commits in the range that affected that file.  In
particular if one of the commits removes the file, previous modifying
commits are not shown.

I found this in the current linux-next tree (next-20080229).

git log stable.. -- arch/avr32/kernel/semaphore.c

will show the commit that removes this file, but not the commit that
modifies it.  So, is this a bug in git log or my understanding?

If you do "git log -p stable.." and search for the file name, you will
find the other commit.

git version 1.5.4.3 from Debian unstable.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/