From: Jeff King <peff@peff.net>
To: Alexander Pepper <pepper@inf.fu-berlin.de>
Cc: git@vger.kernel.org
Subject: Re: Bug?: 'git log --find-copies' doesn't match 'git log --follow <rev> -- path/to/file'
Date: Fri, 30 Sep 2011 17:38:41 -0400 [thread overview]
Message-ID: <20110930213841.GA9384@sigill.intra.peff.net> (raw)
In-Reply-To: <DBC73B3F-2703-4651-AADA-233A9CC38AFD@inf.fu-berlin.de>
On Fri, Sep 30, 2011 at 05:32:38PM +0200, Alexander Pepper wrote:
> So git log with copy and rename detection on (--find-copies) tells me,
> that the file StopClusterException.java is copied to
> ClusterOperation.java. But If I ask git log for that specific file
> with --follow git claims a copy from Immutable.java to
> ClusterOperation.java!
I think that --follow uses --find-copies-harder. Did you try:
git log --numstat --find-copies-harder dd4e90f9
? Does it find Immutable.java as the source?
-Peff
next prev parent reply other threads:[~2011-09-30 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 15:32 Bug?: 'git log --find-copies' doesn't match 'git log --follow <rev> -- path/to/file' Alexander Pepper
2011-09-30 21:38 ` Jeff King [this message]
2011-10-02 15:10 ` Alexander Pepper
2011-10-02 15:25 ` Jeff King
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=20110930213841.GA9384@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pepper@inf.fu-berlin.de \
/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).