From: Michael J Gruber <git@drmicha.warpmail.net>
To: Mike Hommey <mh@glandium.org>, git@vger.kernel.org
Subject: Re: Score in diff-format
Date: Wed, 28 Jan 2015 15:32:38 +0100 [thread overview]
Message-ID: <54C8F306.1000001@drmicha.warpmail.net> (raw)
In-Reply-To: <20150128062309.GA29506@glandium.org>
Mike Hommey schrieb am 28.01.2015 um 07:23:
> Hi,
>
> diff-format.txt says this:
>
> An output line is formatted this way:
> (snip)
>
> That is, from the left to the right:
>
> (snip)
> . status, followed by optional "score" number.
>
> (snip)
> Status letters C and R are always followed by a score (denoting the
> percentage of similarity between the source and target of the move or
> copy), and are the only ones to be so.
>
> As I read this last paragraph, the following is not supposed to happen:
> $ git diff-tree 926b1ec63ee045503f609e88ca445b94c06bd5d7 --abbrev -r -C -B
> 926b1ec63ee045503f609e88ca445b94c06bd5d7
> :100644 100644 81ac702... 7ab0cf4... M087 contrib/subtree/INSTALL
>
> It however makes sense that it happens, and it looks like a case of the
> documentation being outdated or confusing. Or am I interpreting it wrong?
I'd say it depends on the definition of "so". The documentation is
correct if you read "so" as "*always* followed by a score". I guess you
read it as "followed by a score".
Percentages with M are not mentioned in diff-format, but they are a
consequence of "-B" processing. Maybe we could mention that?
Michael
next prev parent reply other threads:[~2015-01-28 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 6:23 Score in diff-format Mike Hommey
2015-01-28 14:32 ` Michael J Gruber [this message]
2015-01-28 21:17 ` Junio C Hamano
2015-01-29 1:22 ` Mike Hommey
2015-01-29 6:20 ` Junio C Hamano
2015-01-28 18:57 ` 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=54C8F306.1000001@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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