From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Kernel.org Tools" <tools@linux.kernel.org>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH b4 0/3] ez: allow sending all versions of a patch series in the same thread
Date: Mon, 27 Feb 2023 16:37:00 -0500 [thread overview]
Message-ID: <20230227213700.5daxue6votxduicp@meerkat.local> (raw)
In-Reply-To: <167753375541.1113499.10387934728460538344.b4-ty@linuxfoundation.org>
On Mon, Feb 27, 2023 at 04:35:55PM -0500, Konstantin Ryabitsev wrote:
> > This series allows that workflow in b4 by adding a '--same-thread'
> > option to 'b4 send', with an associated config option.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] ez: allow sending all versions of a patch series in the same thread
> commit: 14a6165754778b83cdfb0b546f5bf23cecb84744
Hm... I found a bug in my own code. :) I took the v2 of the series, with
slight modifications (which is why auto-matching failed).
Anyway, v2 is in.
-K
prev parent reply other threads:[~2023-02-27 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 1:29 [PATCH b4 0/3] ez: allow sending all versions of a patch series in the same thread Philippe Blain
2023-02-22 1:29 ` [PATCH b4 1/3] ez: allow iterations to be sent in a single thread Philippe Blain
2023-02-22 1:29 ` [PATCH b4 2/3] ez: add '--same-thread' option to 'b4 send' Philippe Blain
2023-02-22 1:29 ` [PATCH b4 3/3] ez: add 'b4.send-same-thread' config for 'b4 send --same-thread' Philippe Blain
2023-02-22 2:25 ` [PATCH b4 0/3] ez: allow sending all versions of a patch series in the same thread Konstantin Ryabitsev
2023-02-22 17:52 ` Philippe Blain
2023-02-24 1:14 ` [PATCH b4 v2] " Philippe Blain
2023-02-27 21:35 ` [PATCH b4 0/3] " Konstantin Ryabitsev
2023-02-27 21:37 ` 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=20230227213700.5daxue6votxduicp@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=levraiphilippeblain@gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).