From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Marc Zyngier <maz@kernel.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [b4][PATCH] Fix handling of series with the [PATCHvX] defect
Date: Tue, 3 Nov 2020 17:30:56 -0500 [thread overview]
Message-ID: <20201103223056.3y4v4n4pkm4gr7xu@chatter.i7.local> (raw)
In-Reply-To: <20201030105153.3015432-1-maz@kernel.org>
On Fri, Oct 30, 2020 at 10:51:53AM +0000, Marc Zyngier wrote:
> b4 tries to handle subject lines such as "[PATCHvX]" by replacing
> the subject line in situ, but seems to do a rather bad job of it,
> resulting in only the first patch of the series being picked up.
> Fetching <20201026134931.28246-1-mark.rutland@arm.com> does exhibit
> the problem.
>
> Fixing the re.sub() expression allows normal funtionalities to be
> restored, and the above series to be fetched.
Thanks, I have no idea how that bad regex made it in. Applied both to
master and stable-0.5.y.
-K
prev parent reply other threads:[~2020-11-03 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 10:51 [b4][PATCH] Fix handling of series with the [PATCHvX] defect Marc Zyngier
2020-11-03 22:30 ` Konstantin Ryabitsev [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=20201103223056.3y4v4n4pkm4gr7xu@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=maz@kernel.org \
--cc=tools@linux.kernel.org \
--cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).