From: Juergen Gross <jgross@suse.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] KVM fixes for v4.12-rc2
Date: Sat, 20 May 2017 12:52:05 +0200 [thread overview]
Message-ID: <97a8ffc4-dd0f-3e2a-0dc4-1ac46c993745@suse.com> (raw)
In-Reply-To: <CA+55aFybQF2pFMWL3_uUZ8sh7xoDd9L4Mw2MzCV_wC_112QXig@mail.gmail.com>
On 20/05/17 00:21, Linus Torvalds wrote:
> So I noticed that my diffstat didn't match either the KVM or the Xen pull.
>
> The *reason* seems to be that both Radim and Juergen have enabled the
> "patience" diff, because if I add "--patience" to the diff line, I get
> the same numbers you guys report.
>
> On Fri, May 19, 2017 at 11:43 AM, Radim Krčmář <rkrcmar@redhat.com> wrote:
>>
>> 28 files changed, 297 insertions(+), 125 deletions(-)
>
> Without "--patience" (the default) I get:
>
> 28 files changed, 292 insertions(+), 120 deletions(-)
>
> which is close, but not the exact same thing.
>
> So I don't mind people using the patience version of the diffing code,
> but on the whole it's a loss as often as it is a win, so I'm wondering
> _why_ you do this? Is there some other project that has started
> suggesting using the patience diff (either with a command line option
> or by just doing
>
> git config diff.algorithm patience
>
> anyway, it's not a big deal, I'm just curious..
In my case it was a patch which was much easier to review using the
patience diff. I just didn't switch back afterwards (what I did now).
Juergen
next prev parent reply other threads:[~2017-05-20 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 18:43 Radim Krčmář
2017-05-19 22:21 ` Linus Torvalds
2017-05-20 10:52 ` Juergen Gross [this message]
2017-05-22 14:37 ` Radim Krčmář
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=97a8ffc4-dd0f-3e2a-0dc4-1ac46c993745@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®