From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: Harry Putnam <reader@newsguy•com>,
"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: Not understanding with git wants to copy one file to another
Date: Mon, 14 Aug 2017 12:21:33 -0700 [thread overview]
Message-ID: <xmqqfucuuf9e.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kaCuaxgGwuw7AHKTjsmwsTBuv=gWzeGDJv3TJv+b25Uvw@mail.gmail.com> (Stefan Beller's message of "Mon, 14 Aug 2017 11:07:29 -0700")
Stefan Beller <sbeller@google•com> writes:
> On Fri, Aug 11, 2017 at 1:41 PM, Harry Putnam <reader@newsguy•com> wrote:
>> Stefan Beller <sbeller@google•com> writes:
>>
>>
>> [...]
>>
>>> Ah. Sorry for confusing even more.
>>> By pointing out the options for git-diff, I just wanted to point out that
>>> such a mechanism ("rename/copy detection") exists.
>>
>>
>> [...]
>>
>>>> What am I missing?
>>>>
>>>
>>> https://www.reddit.com/r/git/comments/3ogkk1/beginner_disable_rename_detection/
>>>
>>> "Rename detection is just GUI sugar".
>>
>> Thanks there is a nice full explanation at the cited url.
>>
>> What is still a bit puzzling is that in that same commit, there are
>> files that are true copies of each other, just in different locations,
>> But nothing pops up about them in a git commit.
>>
>
> The heuristic to find the renames/copies only looks at modified files
> to be fast(, the assumption is that each commit only touches few
> files, but the project consists of a lot of files).
>
> For that git-diff knows about '--find-copies-harder' that looks at
> all files even those not modified. This would point out the true
> copies, I would assume.
>
> I don't think we'd want to include the '--find-copies-harder' flag
> to status or commit, as it may take some time in large projects.
Yeah, thanks for helping in this discussion.
prev parent reply other threads:[~2017-08-14 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 17:03 Not understanding with git wants to copy one file to another Harry Putnam
2017-08-10 17:36 ` Stefan Beller
2017-08-10 18:18 ` Harry Putnam
2017-08-10 18:47 ` Stefan Beller
2017-08-11 20:41 ` Harry Putnam
2017-08-14 18:07 ` Stefan Beller
2017-08-14 19:21 ` Junio C Hamano [this message]
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=xmqqfucuuf9e.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=reader@newsguy$(echo .)com \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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