From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4-0.9.0 available
Date: Mon, 20 Jun 2022 10:40:34 +0200 [thread overview]
Message-ID: <CAMuHMdV54SN7ghTTUnba+3p_9M2NkcXQ6R8KzQXEsWfPWXD6mg@mail.gmail.com> (raw)
In-Reply-To: <20220617190153.tvi5lkzlvemeqou5@meerkat.local>
Hi Konstantin,
On Fri, Jun 17, 2022 at 9:02 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> After a bit of a hiatus, I am finally able to work on b4 again, so here's
> version 0.9.0 that implements one major new feature and adds some other
> improvements to existing features.
Thanks for your continued support on improving our workflow!
> # new: b4 shazam
>
> This command is very similar to "b4 am", but it allows you to apply patches
> directly to the git repository without the need pipe the output of "b4 am" to
> "git am".
>
> The shazam command has three modes of operation:
>
> 1. default mode that applies patches directly to your git repository, just
> like passing the .mbox file to git-am
> 2. with -H, shazam will try to prepare the patch series into FETCH_HEAD, which
> can then be checked out into a branch or merged with git-merge. This
> effectively makes patch series work similar to pull requests.
> 3. with -M, shazam will do the same as with -H, but will also exec git-merge
> with the cover letter prepared as part of the merge commit message. You can
> see it in action here: https://asciinema.org/a/502421
So if I want to run checkpatch, I have to keep on using "b4 am"
and "git am" separately, right? I never apply patches without running
checkpatch first[1].
Perhaps "b4 shazam" could gain some --checker option to support this?
Thanks!
[1] Currently I use "cat *mbx | formail -s scripts/checkpatch.pl".
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-06-20 8:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 19:01 b4-0.9.0 available Konstantin Ryabitsev
2022-06-20 8:40 ` Geert Uytterhoeven [this message]
2022-06-21 23:38 ` Linus Walleij
2022-06-22 5:49 ` Vinod Koul
2022-06-21 15:20 ` Geert Uytterhoeven
2022-06-21 15:29 ` Konstantin Ryabitsev
2022-06-21 15:41 ` Geert Uytterhoeven
2022-06-21 15:55 ` Linus Torvalds
2022-06-21 16:03 ` Jason A. Donenfeld
2022-06-21 16:59 ` Konstantin Ryabitsev
2022-06-21 17:49 ` Jason A. Donenfeld
2022-06-21 18:29 ` Konstantin Ryabitsev
2022-06-21 18:45 ` Jason A. Donenfeld
2022-06-21 19:27 ` Konstantin Ryabitsev
2022-06-21 19:42 ` Jason A. Donenfeld
2022-06-21 19:43 ` Geert Uytterhoeven
2022-06-21 19:50 ` Jason A. Donenfeld
2022-06-21 20:06 ` Konstantin Ryabitsev
2022-06-21 20:29 ` Jason A. Donenfeld
2022-06-21 21:25 ` Bjorn Andersson
2022-06-23 23:33 ` Theodore Ts'o
2022-06-24 13:51 ` Jason Gunthorpe
2022-06-24 15:29 ` Theodore Ts'o
2022-06-24 15:34 ` Mark Brown
2022-06-24 16:05 ` Theodore Ts'o
2022-06-24 15:52 ` Konstantin Ryabitsev
2022-06-24 16:05 ` James Bottomley
2022-06-24 16:16 ` Konstantin Ryabitsev
2022-06-24 16:29 ` James Bottomley
2022-06-24 16:06 ` Jason Gunthorpe
2022-06-24 16:16 ` Mark Brown
2022-06-24 17:51 ` Chuck Lever
2022-06-24 8:34 ` Nicolas Ferre
2022-06-21 15:53 ` Jason A. Donenfeld
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=CAMuHMdV54SN7ghTTUnba+3p_9M2NkcXQ6R8KzQXEsWfPWXD6mg@mail.gmail.com \
--to=geert@linux-m68k.org \
--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 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.