From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Alexander Litvinov <litvinov2004@gmail.com>
Subject: Re: Rename detection at git log
Date: Mon, 20 Nov 2006 10:50:55 +0100 [thread overview]
Message-ID: <200611200951.05529.andyparkins@gmail.com> (raw)
In-Reply-To: <200611201157.23680.litvinov2004@gmail.com>
On Monday 2006 November 20 05:57, Alexander Litvinov wrote:
> > PAGER=cat git log -M -C --pretty=oneline b/a
I've come across this too. Personally I'm not sure what use "-C" is. From
the manpage, man git-diff-files (no, this isn't the place I'd look either).
--find-copies-harder
For performance reasons, by default, -C option finds copies only if the
original file of the copy was modified in the same changeset. This flag makes
the command inspect unmodified files as candidates for the source of copy.
This is a very expensive operation for large projects, so use it with
caution.
That is to say that unless the file you are copying was modified AND copied in
the same commit, it won't be searched as a potential source for the copy
operation. I think it would be rare to make a copy of a file I had modified,
surely I'd want to check in modifications before making a copy?
Regardlss, to get the results you want, use the stronger
switch --find-copies-harder, heeding the warning that on big projects it will
be very slow.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-11-20 9:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 5:57 Rename detection at git log Alexander Litvinov
2006-11-20 9:50 ` Andy Parkins [this message]
2006-11-20 10:07 ` Junio C Hamano
2006-11-20 10:11 ` Jakub Narebski
2006-11-20 10:22 ` Andy Parkins
2006-11-20 10:48 ` Junio C Hamano
2006-11-20 11:01 ` Andy Parkins
2006-11-20 11:15 ` Jakub Narebski
2006-11-20 11:32 ` Junio C Hamano
2006-11-20 11:59 ` Andy Parkins
2006-11-20 11:28 ` Junio C Hamano
2006-11-20 12:16 ` Andy Parkins
2006-11-20 11:33 ` Alexander Litvinov
2006-11-20 10:06 ` Alex Riesen
2006-11-20 10:23 ` Andy Parkins
2006-11-20 10:51 ` Junio C Hamano
2006-11-20 11:17 ` Andy Parkins
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=200611200951.05529.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=litvinov2004@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).