Bug in git log

From: Matthias Kestenholz <hidden>
Date: 2016-06-15 22:42:25

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help