From: Matthias Kestenholz <lists@irregular.ch>
To: git@vger.kernel.org
Subject: Bug in git log
Date: Tue, 2 May 2006 09:51:22 +0200 [thread overview]
Message-ID: <20060502075122.GA8203@spinlock.ch> (raw)
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 reply other threads:[~2006-05-02 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 7:51 Matthias Kestenholz [this message]
2006-05-02 8:24 ` Bug in git log Junio C Hamano
2006-05-02 13:41 ` Matthias Kestenholz
2006-05-02 15:26 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060502075122.GA8203@spinlock.ch \
--to=lists@irregular.ch \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.