From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: New version of lore available for preview
Date: Thu, 9 Sep 2021 16:51:14 +0200 [thread overview]
Message-ID: <YTofYpb5U1cn66M9@piout.net> (raw)
In-Reply-To: <YToQEQPcjU5RUww7@google.com>
On 09/09/2021 14:45:53+0100, Lee Jones wrote:
> On Thu, 09 Sep 2021, Konstantin Ryabitsev wrote:
>
> > On Thu, Sep 09, 2021 at 02:32:25PM +0100, Lee Jones wrote:
> > > In my current implementation, I have pwclient pull down the patch,
> > > apply my SoB and apply the it, all in one foul swoop:
> > >
> > > pwclient git-am -p ${project} -3 -s ${pwid}
> > >
> > > Does b4 provide this functionality too, or do I have to script around
> > > it? How have other's chosen to automatically apply the downloaded
> > > mboxes?
> >
> > b4 am -3 -s -o- msgid | git am
>
> Ah yes, piping to stdout and straight into Git works great.
>
> And with "-P _", it does exactly what I want.
>
I did use the stdout piping to git am until I have seen someone on a
mailing list adding this to .gitconfig
[alias]
b4am = "!sh -c 'b4 am -ctsl -o- $1 | git am' -"
b4am1 = "!sh -c 'b4 am -ctsl -o- -P_ $1 | git am' -"
and then you can directly do git b4am <msg-id>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-09-09 15:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:07 New version of lore available for preview Konstantin Ryabitsev
2021-08-18 19:09 ` Jason A. Donenfeld
2021-08-18 19:48 ` Konstantin Ryabitsev
2021-08-18 19:50 ` Junio C Hamano
2021-08-25 16:30 ` Rob Herring
2021-08-25 16:44 ` Konstantin Ryabitsev
2021-08-25 21:39 ` Josh Triplett
2021-08-26 14:04 ` Konstantin Ryabitsev
2021-08-26 23:04 ` Josh Triplett
2021-09-02 19:53 ` Jason Gunthorpe
2021-09-02 20:14 ` Konstantin Ryabitsev
2021-09-02 22:44 ` Masahiro Yamada
2021-09-03 10:30 ` Mark Brown
2021-09-03 15:21 ` Konstantin Ryabitsev
2021-09-06 9:59 ` Lee Jones
2021-09-08 18:37 ` Konstantin Ryabitsev
2021-09-09 12:49 ` Steven Rostedt
2021-09-09 13:32 ` Lee Jones
2021-09-09 13:38 ` Konstantin Ryabitsev
2021-09-09 13:45 ` Lee Jones
2021-09-09 14:39 ` Konstantin Ryabitsev
2021-09-09 15:24 ` James Bottomley
2021-09-09 16:17 ` Konstantin Ryabitsev
2021-09-09 14:51 ` Alexandre Belloni [this message]
2021-09-09 15:00 ` Konstantin Ryabitsev
2021-09-09 13:43 ` Greg KH
2021-09-09 13:54 ` Lee Jones
2021-09-09 13:56 ` Mark Brown
2021-09-09 14:05 ` Lee Jones
2021-09-10 16:07 ` Bjorn Andersson
2021-09-10 16:12 ` Mark Brown
2021-09-10 17:21 ` Peter Zijlstra
2021-09-09 13:55 ` Steven Rostedt
2021-09-09 14:04 ` Lee Jones
2021-09-09 14:51 ` Peter Zijlstra
2021-09-10 6:10 ` Lee Jones
2021-09-02 23:38 ` Jason Gunthorpe
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=YTofYpb5U1cn66M9@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=jgg@nvidia.com \
--cc=konstantin@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=masahiroy@kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).