Thread (16 messages) flat view 16 messages, 3 authors, 2016-06-15

Re: Re: git log -M -- filename is not working?

From: Jeff King <hidden>
Date: 2016-06-15 22:48:47

Possibly related (same subject, not in this thread)

On Thu, May 13, 2010 at 12:07:24AM +0800, Bo Yang wrote:
quoted
But with `-p' it was doing something confusing: I used two files that
were recently renamed, and the result was the correct log history, but
the first patch that was shown (the rename) showed the two files as
added.  (That's even when I added `-C' and `-M'.)  This happens even
with a single path.  OTOH, using `--follow' with `-p' and a single
path without your patch produces the expected result where the first
patch is a rename (even without `-C'/`-M').
Try this one, it only change a little on Jeff's patch, my simple tests
show it works. Apply it on 'next' branch.
This is badly whitespace damaged. I fixed up some wrapping, but it seems
that there was some tab/space interchanges, too. Can you repost?

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help