From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: andrew.cooper3@citrix.com, konstantin@linuxfoundation.org,
tools@linux.kernel.org
Subject: Re: b4 patch corruption
Date: Wed, 6 Sep 2023 21:09:10 +0000 (UTC) [thread overview]
Message-ID: <20230906-b217852c3-6ae369988340@bugzilla.kernel.org> (raw)
In-Reply-To: <c9643b70-8751-a2a2-185e-174ec2560328@citrix.com>
Konstantin Ryabitsev writes in commit 0438c6a107d3475895281146e51d68069a41dc3d:
am: properly handle non-git diffs
We were not properly parsing patches generated by something other than
"git diff" or "git format-patch". Notably, these are pretty rare, but we
still shouldn't fail when doing that.
This additionally adds a few tests and fixes a silly mistake that I had
all along in the sample data.
Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217852
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
(via https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=0438c6a107d3)
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
prev parent reply other threads:[~2023-09-06 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 12:23 b4 patch corruption Andrew Cooper
2023-08-31 20:26 ` Konstantin Ryabitsev
2023-08-31 20:32 ` Kernel.org Bugbot
2023-09-06 21:09 ` Kernel.org Bugbot [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=20230906-b217852c3-6ae369988340@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.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 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.