From: Junio C Hamano <gitster@pobox•com>
To: Nick Desaulniers <ndesaulniers@google•com>
Cc: Jeff King <peff@peff•net>, Stefan Beller <sbeller@google•com>,
"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: fuzzy patch application
Date: Fri, 10 Feb 2017 19:09:56 -0800 [thread overview]
Message-ID: <xmqqd1epifsr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAKwvOdmvYiu4ApxL7jVh_0WZUMVeC2jJ4Q_Zs5Z5-J6GNH8DdQ@mail.gmail.com> (Nick Desaulniers's message of "Fri, 10 Feb 2017 14:56:11 -0800")
Nick Desaulniers <ndesaulniers@google•com> writes:
> For the dangers related to fuzzing, is there more info? I found
> and old post on this from Linus calling fuzzing dangerous but
> from what I could tell about my patch that wouldn't apply
> without fuzzing, the only difference in bad hunks was
> whitespace that had diverged somehow.
If the "old post" is the one he explains why he chose not to allow
fuzz by default, I think you got all what you need. Basically, he
wanted you and his users to make sure that the patch they are having
trouble with applying can be due to only insignificant difference
and it is safe to apply with reduced context, instead of blindly
accepting a fuzzy patch application.
prev parent reply other threads:[~2017-02-11 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 19:20 fuzzy patch application Nick Desaulniers
2017-02-10 19:38 ` Junio C Hamano
2017-02-10 20:57 ` Jeff King
2017-02-10 21:37 ` Stefan Beller
2017-02-10 21:48 ` Jeff King
2017-02-10 22:31 ` Junio C Hamano
2017-02-10 22:53 ` Junio C Hamano
2017-02-10 22:56 ` Nick Desaulniers
2017-02-11 3:09 ` 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=xmqqd1epifsr.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ndesaulniers@google$(echo .)com \
--cc=peff@peff$(echo .)net \
--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