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

Re: git blame --reverse: it's all a bit mysterious

From
Thomas Rast <trast@student.ethz.ch>
Date
Nov 11, 2010, 22:15 UTC
Message-ID
<201011112315.04299.trast@student.ethz.ch>
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
Previous: Robin Green
Message 2 of 2 in “git blame --reverse: it's all a bit mysterious”
  1. Robin GreenNov 11, 2010
  2. Thomas RastNov 11, 2010

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.