From: Harry Putnam <reader@newsguy•com>
To: git@vger•kernel.org
Subject: Re: Not understanding with git wants to copy one file to another
Date: Thu, 10 Aug 2017 14:18:12 -0400 [thread overview]
Message-ID: <87efsj70d7.fsf@local.lan> (raw)
In-Reply-To: CAGZ79kbgb2P7KT_b9xuMj1pN1+jsPfH7YSJNDyDB5dY3cwXCQg@mail.gmail.com
Stefan Beller <sbeller@google•com> writes:
> On Thu, Aug 10, 2017 at 10:03 AM, Harry Putnam <reader@newsguy•com> wrote:
[...]
Harry wrote:
>> Here are two that are at least kind of similar but would never be seen
>> as the same:
>>
>> < 192.168.1.43 m2.local.lan m2 # 00-90-F5-A1-F9-E5
>>> 192.168.1.43 m2.local.lan m2 # win 7
Stefan B replied:
> The diff machinery has a threshold for when it assumes
> a copy/move of a file. (e.g. "A file is assumed copied when
> at least 55% of lines are equal")
>
> https://git-scm.com/docs/git-diff
>
> See -C and -M option.
>
> git-status seems to use this machinery as well, but does
> not expose the options?
Well, now I'm even more confused. What actually happens? Is either
file changed? Is only one file kept?
On the surface it sounds like complete anathema to what git is all
about.
However, I know a tool this sophisticated is not doing something just
outright stupid... so must be really missing the point here.
I get the way you can make -M stricter or not... but I didn't call
git-diff to see that copy thing comeup.
I called git commit.
There must be some way to set stricter guidlines to calling things
copies.
But then I must really not get it because it still seems almost silly
to consider one file a copy of another if only 55% is the same.
What am I missing?
next prev parent reply other threads:[~2017-08-10 18:18 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 [this message]
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
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=87efsj70d7.fsf@local.lan \
--to=reader@newsguy$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/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