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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]