git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Anomaly in git log?

From
SRStephen Rothwell <sfr@canb.auug.org.au>
Date
Mar 1, 2008, 02:35 UTC
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/
Next: Shawn O. Pearce
Message 1 of 2 in “Anomaly in git log?”
  1. Stephen RothwellMar 1, 2008
  2. Shawn O. PearceMar 1, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.