| Message ID | 20230219-send-iterations-in-same-thread-v1-0-59b802382eb5@gmail.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | ez: allow sending all versions of a patch series in the same thread | expand |
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
Hi Konstantin, Le 2023-02-21 à 21:25, Konstantin Ryabitsev a écrit : > 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. Yeah, I agree this will usually be a "set it once for this project and forget" kind of thing, so it makes sense for it to be only settable in the config. I will do that for v2. Thanks, Philippe.
On Tue, 21 Feb 2023 20:29:16 -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. > > [...] Applied, thanks! [1/1] ez: allow sending all versions of a patch series in the same thread commit: 14a6165754778b83cdfb0b546f5bf23cecb84744 Best regards,
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
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. Cheers, Philippe. [1] https://git-scm.com/docs/MyFirstContribution#v2-git-send-email --- Philippe Blain (3): ez: allow iterations to be sent in a single thread ez: add '--same-thread' option to 'b4 send' ez: add 'b4.send-same-thread' config for 'b4 send --same-thread' b4/command.py | 2 ++ b4/ez.py | 14 ++++++++++++-- docs/config.rst | 4 ++++ docs/contributor/send.rst | 5 +++++ 4 files changed, 23 insertions(+), 2 deletions(-) --- base-commit: a3281834d6d5dec44f58071fca2d22e04a97fe18 change-id: 20230219-send-iterations-in-same-thread-c50a3bc4ed9e -- b4