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

Bug in git log

From
MKMatthias Kestenholz <lists@irregular.ch>
Date
May 2, 2006, 07:51 UTC
Message-ID
<20060502075122.GA8203@spinlock.ch>
Hello list,

I found a bug in the new builtin git log which I am unable to fix myself.

Inside your git source directory, do:
First bug using old whatchanged script (not builtin version)

$ ./git-whatchanged.sh -- unresolve.c fatal: ambiguous argument 'unresolve.c': unknown revision or filename Use '--' to separate filenames from revisions

$ ./git-whatchanged.sh -- -- unresolve.c [...] gives the expected output

$ git log -- unresolve.c $ git log -- -- unresolve.c $ git whatchanged -- unresolve.c

both give no output.

I checked the argument parsing stage and everything seemed sane (the second double-dash was not necessary anymore)

However, the following works as expected:
$ git log -- git-log.sh

It seems that the problem shows only if there was no commit modifying the asked-for file. unresolve.c is introduced in commit ec167793d84ba7b765e1eb71b0257ce7baca2d26 and removed in the subsequent commit 2bd452d3b9f62ecc3406307cd6a5553856d21ff2 and is never modified.

/Matthias
-- 
:wq
Next: Junio C Hamano
Message 1 of 4 in “Bug in git log”
  1. Matthias KestenholzMay 2, 2006
  2. Junio C HamanoMay 2, 2006
  3. Matthias KestenholzMay 2, 2006
  4. Linus TorvaldsMay 2, 2006

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.