From: Thomas Rast <trast@student.ethz.ch>
To: Robin Green <greenrd@greenrd.org>
Cc: <git@vger.kernel.org>
Subject: Re: git blame --reverse: it's all a bit mysterious
Date: Thu, 11 Nov 2010 23:15:04 +0100 [thread overview]
Message-ID: <201011112315.04299.trast@student.ethz.ch> (raw)
In-Reply-To: <87hbfnabax.wl%greenrd@greenrd.org>
Robin Green wrote:
> greenrd@cspcnh /var/db/paludis/repositories/arbor $ strace -f -e trace=file git blame --reverse 48d96ce0e486eedea9fda0f8e480ba3c6caffc90..HEAD exlibs/eutils.exlib
[...]
> I notice from the strace output that it's looking for the specified filename first, which of course
> no longer exists in HEAD.
This can be fixed by saying
git blame --reverse 48d96ce0e486eedea9fda0f8e480ba3c6caffc90..HEAD -- exlibs/eutils.exlib
i.e., you need to supply the -- to explicitly tell it that the stuff
after it is a filename.
It's probably a code (not documentation) bug since blame takes only a
single revision range anyway, so everything after that should be
assumed to be a filename, but maybe I'm missing something.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2010-11-11 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 19:51 git blame --reverse: it's all a bit mysterious Robin Green
2010-11-11 22:15 ` Thomas Rast [this message]
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=201011112315.04299.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=greenrd@greenrd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).