From: Jeff King <peff@peff.net>
To: Bo Yang <struggleyb.nku@gmail.com>
Cc: Eli Barzilay <eli@barzilay.org>,
Junio C Hamano <gitster@pobox.com>,
Eugene Sajine <euguess@gmail.com>,
Jacob Helwig <jacob.helwig@gmail.com>,
git@vger.kernel.org
Subject: Re: Re: git log -M -- filename is not working?
Date: Wed, 12 May 2010 12:45:22 -0400 [thread overview]
Message-ID: <20100512164522.GA14710@coredump.intra.peff.net> (raw)
In-Reply-To: <AANLkTilje2dBHjd2aykMnAjWdf8k1vayJ_ez4IfMrl7_@mail.gmail.com>
On Thu, May 13, 2010 at 12:07:24AM +0800, Bo Yang wrote:
> > 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
next prev parent reply other threads:[~2010-05-12 16:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 18:07 git log -M -- filename is not working? Eugene Sajine
2010-05-07 18:10 ` Jacob Helwig
2010-05-07 18:31 ` Eugene Sajine
2010-05-07 18:37 ` Eli Barzilay
2010-05-07 20:25 ` Matthieu Moy
2010-05-07 20:28 ` Jakub Narebski
2010-05-08 4:44 ` Jeff King
2010-05-08 5:12 ` Eli Barzilay
2010-05-08 5:30 ` Jeff King
2010-05-08 5:39 ` Junio C Hamano
2010-05-08 7:08 ` Eli Barzilay
2010-05-12 11:38 ` Jeff King
2010-05-12 12:01 ` Eli Barzilay
2010-05-12 12:49 ` Jeff King
2010-05-12 13:03 ` Jeff King
2010-05-12 14:35 ` Eli Barzilay
2010-05-12 16:07 ` Bo Yang
2010-05-12 16:45 ` Jeff King [this message]
2010-05-13 2:12 ` Bo Yang
2010-05-13 4:39 ` Eli Barzilay
2010-05-14 4:55 ` Jeff King
2010-05-14 5:05 ` Eli Barzilay
2010-05-12 13:06 ` Bo Yang
2010-05-12 13:09 ` Jeff King
2010-05-12 14:42 ` Eli Barzilay
2010-05-12 14:49 ` Bo Yang
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=20100512164522.GA14710@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=eli@barzilay.org \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.helwig@gmail.com \
--cc=struggleyb.nku@gmail.com \
/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).