From: Junio C Hamano <gitster@pobox.com>
To: Jerry Zhang <jerry@skydio.com>
Cc: git@vger.kernel.org, ross@skydio.com, abe@skydio.com,
brian.kubisiak@skydio.com
Subject: Re: [PATCH] git-apply: silence errors for success cases
Date: Tue, 20 Apr 2021 19:14:51 -0700 [thread overview]
Message-ID: <xmqqtuo0z8mc.fsf@gitster.g> (raw)
In-Reply-To: <20210421004733.22395-1-jerry@skydio.com> (Jerry Zhang's message of "Tue, 20 Apr 2021 17:47:33 -0700")
Jerry Zhang <jerry@skydio.com> writes:
> Certain invocations of "git apply --3way"
> will print error messages even though git
> is able to fall back on apply_fragments and
> apply the patch successfully with a return
> value of 0. To fix, return early from
> try_threeway() in the following cases:
I suspect that this is a recent breakage after we swapped the order
of 3way fallback. It used to be that we tried the straight
application first (while suppressing the error messages) and then
fell back on 3way (while fully exposing the error messages).
It is understandable if we just swapped the order without changing
when errors are squelched, we may leak unnecessary error messages
while trying 3way and failing.
After having written all of the above, I just realized that the
swapping of the order was _your_ topic and you didn't have to be
explained any of the above ;-) Just consider it as my thinking
aloud for the benefit of those who are reading from the sideline
(i.e. those not on the To/Cc list but are reading because this
message is sent to git@ mailing list).
next prev parent reply other threads:[~2021-04-21 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 0:47 [PATCH] git-apply: silence errors for success cases Jerry Zhang
2021-04-21 2:14 ` Junio C Hamano [this message]
2021-04-21 23:53 ` Junio C Hamano
2021-07-28 3:14 ` [PATCH V2] " Jerry Zhang
2021-12-11 2:05 ` Jerry Zhang
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=xmqqtuo0z8mc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=abe@skydio.com \
--cc=brian.kubisiak@skydio.com \
--cc=git@vger.kernel.org \
--cc=jerry@skydio.com \
--cc=ross@skydio.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.