From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: b4 submit ready for beta testing
Date: Tue, 26 Jul 2022 16:54:09 +0200 [thread overview]
Message-ID: <87bktbapri.fsf@baylibre.com> (raw)
In-Reply-To: <20220726142743.dllhmbivtb2yk4uk@meerkat.local>
On Tue, Jul 26, 2022 at 10:27, Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Jul 26, 2022 at 10:37:18AM +0200, Mattijs Korpershoek wrote:
>> > 2. "b4 submit" command got split into 3 different commands:
>>
>> While I do agree that these commands make life easier, I don't think
>> that we should "ez-" as a prefix.
>>
>> The "ez-" part has, in my opinion, no added value for users. It
>> assumes that using these commands is so easy that "you can't use it,
>> you're really incompetent". I think we should use more "neutral" langage
>> for commands (without judging if it's easy or difficult).
>
> Yeah, ez- is a gimmick and may not stay. It's easy to type and tab-complete,
> though, which is why I went with that (not that tab completion bits are done
> for b4 yet).
Ok. I really think it should be removed because it gives a judgment on
the user. For some folks it's also "easy" to "just use git send-email".
>
>> How about:
>> - b4 series (for creating/handling series. Also includes "send"/"submit")
>
> I think that makes it hard to distinguish from "b4 am/shazam" that also
> operate on series. In my mind, the command should indicate that it's
> specifically for working on series for submitting them upstream as opposed to
> for retrieving series for inclusion into your repos.
>
> Perhaps "b4 prep"?
Understood. series is indeed ambiguous and "prep" or "prepare" seems
more appropriate.
>
>> - b4 trailers (for handling trailer updates)
>
> Okay, since one of the plans is to add a way for maintainers to quickly send
> their own follow-up trailers, e.g.:
>
> b4 trailers --ack [--trailer 'My-Trailer: Foo Bar <eml@addr.foo>'] <msgid>
>
> this would allow defining keybindings in mutt to quickly submit an "Acked-by"
> or any other trailer.
That looks awesome :)
>
>> > b4 ez-send --no-auto-to-cc --dry-run
>>
>> In my opinion, "b4 send" should be part of series because we cannot send
>> series that were not created with "b4 series".
>
> It won't be limited to just series, though -- you'll soon be able to send pull
> requests as well, and that will accept arbitrary tags. So, I intend to keep it
> separate from "prep".
Ok. I did not think about the pull requests part (I'm an
occasional contributor). It makes sense to keep them separated.
>
> Thanks for your feedback!
>
> -K
next prev parent reply other threads:[~2022-07-26 14:54 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 14:29 b4 submit ready for beta testing Konstantin Ryabitsev
2022-07-16 14:43 ` James Bottomley
2022-07-16 14:56 ` Konstantin Ryabitsev
2022-07-16 16:10 ` Junio C Hamano
2022-07-16 16:55 ` James Bottomley
2022-07-16 17:14 ` Conor Dooley
2022-07-17 15:43 ` Konstantin Ryabitsev
2022-07-18 18:14 ` Jason Gunthorpe
2022-07-18 18:34 ` Luck, Tony
2022-07-17 16:02 ` Konstantin Ryabitsev
2022-07-18 18:17 ` Jason Gunthorpe
2022-07-18 20:28 ` Geert Uytterhoeven
2022-07-18 23:10 ` Jason Gunthorpe
2022-07-19 7:02 ` Geert Uytterhoeven
2022-07-19 12:09 ` Mark Brown
2022-07-19 12:28 ` Geert Uytterhoeven
2022-07-20 13:06 ` Sudeep Holla
2022-07-19 12:44 ` James Bottomley
2022-07-19 12:51 ` Geert Uytterhoeven
2022-07-19 13:11 ` Michael S. Tsirkin
2022-07-19 14:14 ` Mark Brown
2022-07-19 12:34 ` Jason Gunthorpe
2022-07-19 12:47 ` Geert Uytterhoeven
2022-07-19 13:00 ` Jason Gunthorpe
2022-07-19 13:16 ` Geert Uytterhoeven
2022-07-19 13:59 ` Maxime Ripard
2022-07-19 15:32 ` Jason Gunthorpe
2022-07-19 16:07 ` Konstantin Ryabitsev
2022-07-19 16:18 ` Rob Herring
2022-07-19 13:01 ` James Bottomley
2022-07-19 15:34 ` Jason Gunthorpe
2022-07-19 15:38 ` James Bottomley
2022-07-19 15:47 ` Jason Gunthorpe
2022-07-25 12:16 ` Michael S. Tsirkin
2022-07-17 9:58 ` Geert Uytterhoeven
2022-07-17 15:40 ` Konstantin Ryabitsev
2022-07-18 8:49 ` Maxime Ripard
2022-07-18 12:38 ` Paolo Bonzini
2022-07-18 18:20 ` Jason Gunthorpe
2022-07-18 18:26 ` Konstantin Ryabitsev
2022-07-18 14:33 ` Konstantin Ryabitsev
2022-07-18 15:15 ` Maxime Ripard
2022-07-18 17:15 ` Rob Herring
2022-07-18 18:23 ` Konstantin Ryabitsev
2022-07-19 12:23 ` Mattijs Korpershoek
2022-07-19 13:09 ` Konstantin Ryabitsev
2022-07-20 18:48 ` Konstantin Ryabitsev
2022-07-20 19:24 ` Jason Gunthorpe
2022-07-20 19:40 ` Konstantin Ryabitsev
2022-07-20 19:55 ` Jason Gunthorpe
2022-07-20 20:06 ` Konstantin Ryabitsev
2022-07-20 23:13 ` Junio C Hamano
2022-07-20 23:23 ` Linus Torvalds
2022-07-20 23:39 ` Jason Gunthorpe
2022-07-20 23:40 ` Linus Torvalds
2022-07-20 23:42 ` Junio C Hamano
2022-07-21 0:02 ` Jason Gunthorpe
2022-07-21 0:54 ` Theodore Ts'o
2022-07-21 2:31 ` Dave Chinner
2022-07-21 13:07 ` Jason Gunthorpe
2022-07-21 22:49 ` Dave Chinner
2022-07-22 9:10 ` Geert Uytterhoeven
2022-07-21 8:48 ` Geert Uytterhoeven
2022-07-21 13:08 ` Jason Gunthorpe
2022-07-26 8:37 ` Mattijs Korpershoek
2022-07-26 13:55 ` Paolo Bonzini
2022-07-26 14:06 ` Konstantin Ryabitsev
2022-07-26 14:27 ` Konstantin Ryabitsev
2022-07-26 14:54 ` Mattijs Korpershoek [this message]
2022-07-26 20:56 ` Konstantin Ryabitsev
2022-08-18 19:30 ` Conor Dooley
2022-08-18 20:12 ` Conor Dooley
2022-08-18 21:04 ` Konstantin Ryabitsev
2022-08-18 21:22 ` Conor Dooley
2022-08-19 20:43 ` Konstantin Ryabitsev
2022-08-19 21:00 ` Conor Dooley
2022-07-26 13:11 ` Mattijs Korpershoek
2022-07-26 14:37 ` Konstantin Ryabitsev
2022-07-28 16:04 ` Maxime Ripard
2022-07-28 16:24 ` Konstantin Ryabitsev
2022-08-15 16:17 ` Maxime Ripard
2022-08-15 17:05 ` Konstantin Ryabitsev
2022-08-16 7:39 ` Maxime Ripard
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=87bktbapri.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=konstantin@linuxfoundation.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