From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Arnott <andrewarnott@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Intensive rename detection
Date: Mon, 3 Nov 2008 20:22:34 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811032021210.3419@nehalem.linux-foundation.org> (raw)
In-Reply-To: <216e54900811031718o4cc81294sc0c32be1e71b9372@mail.gmail.com>
On Mon, 3 Nov 2008, Andrew Arnott wrote:
>
> I'm refactoring a library including renaming both files and
> directories. A few lines of each file are also changed, but they are
> substantially unchanged in content. I've done a git add to put all my
> changes into the index, but a git status shows that git only detected
> a few of the renames... most of them are delete-add operations. Is
> there anything I can do to help git recognize the rename so that
> history is preserved across this commit?
How many renames do you have? Modern versions of git will do any number of
exact renames, but the (rather expensive) inexact rename detection has a
default limit of something fairly small.
You could try adding
[diff]
renamelimit=0
to your ~/.gitconfig file. It can be quite expensive though.
Linus
next prev parent reply other threads:[~2008-11-04 4:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <216e54900811031717j70669868p3c7503357ceb5138@mail.gmail.com>
2008-11-04 1:18 ` Intensive rename detection Andrew Arnott
2008-11-04 1:39 ` Junio C Hamano
2008-11-04 4:22 ` Linus Torvalds [this message]
2008-11-04 4:23 ` Linus Torvalds
2008-11-04 4:31 ` Jeff King
[not found] ` <216e54900811032107p159e98ecn8958f0a78efde8f2@mail.gmail.com>
2008-11-04 5:19 ` Andrew Arnott
2008-11-04 6:02 ` Andrew Arnott
2008-11-04 6:16 ` Jeff King
2008-11-04 6:36 ` Andrew Arnott
2008-11-04 10:47 ` Björn Steinbrink
2008-11-05 3:22 ` 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=alpine.LFD.2.00.0811032021210.3419@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=andrewarnott@gmail.com \
--cc=git@vger.kernel.org \
/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).