From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Philippe Blain <levraiphilippeblain@gmail.com>
Cc: "Kernel.org Tools" <tools@linux.kernel.org>
Subject: Re: [PATCH b4 0/3] ez: allow sending all versions of a patch series in the same thread
Date: Tue, 21 Feb 2023 21:25:25 -0500 [thread overview]
Message-ID: <20230222022525.p7jtphm7rc4dfurw@meerkat.local> (raw)
In-Reply-To: <20230219-send-iterations-in-same-thread-v1-0-59b802382eb5@gmail.com>
On Tue, Feb 21, 2023 at 08:29:16PM -0500, Philippe Blain wrote:
> Sending a new iteration of a series in the same thread as the previous
> one is the preferred workflow on some lists, the Git mailing list being
> an example [1].
>
> This series allows that workflow in b4 by adding a '--same-thread'
> option to 'b4 send', with an associated config option.
Thanks, Philippe.
I think I prefer to *just* have this be set in config, without the CLI switch.
The goal is to make "b4 prep" workflow be friendly to newbies, so having
--help output a ton of options is the situation I want to avoid.
I'll take this in if you drop the --same-thread switch.
Cheers,
-K
next prev parent reply other threads:[~2023-02-22 2:25 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 ` Konstantin Ryabitsev [this message]
2023-02-22 17:52 ` [PATCH b4 0/3] ez: allow sending all versions of a patch series in the same thread 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
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=20230222022525.p7jtphm7rc4dfurw@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 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.