Re: Can git log <file> follow log of its origins?

--- Junio C Hamano wrote:

Max Pollard writes:

quoted

I only see the log corresponding to the 2nd commit (v1.5.3.5).

That is what you are asking "git log" to show.  "git log b.txt"
means "please simplify the history by throwing away commits that
do not have changes to paths that match b.txt, and then show the
resulting log with the change pertaining to that path".  The
first commit does not change a path called b.txt (in other
words, "git show --stat HEAD^" will not give diffstat for "b.txt"),
so that commit is not shown.

$ git log --pretty=oneline --name-status -C -C

Got it - many thanks.  So -C -C is the answer, with --name-status or --stat to
actually show the result.  From the code, a status like Cxxx appears to contain
the "similarity percentage" in xxx; so that C100 would mean an exact copy...


MP



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ