From: Peter Zijlstra <peterz@infradead.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4 v0.11.0 available
Date: Tue, 20 Dec 2022 21:40:09 +0100 [thread overview]
Message-ID: <Y6IdqeOfLMrBrFiL@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20221219213715.2qozw5emt5j7t3xr@nitro.local>
On Mon, Dec 19, 2022 at 04:37:15PM -0500, Konstantin Ryabitsev wrote:
> Special thanks to the following people who helped with this release, in
> reverse-git order:
> Peter Zijlstra <peterz@infradead.org>
For whoever cares; the below is part of my .muttrc that uses the new
feature:
set pipe_split=no
set pipe_sep="\n---9094415c807d3d9a7e592fe6307c363eec028754---\n"
macro index B "<tag-prefix><pipe-entry>b4 am -slt --stdin-pipe-sep='\\n---9094415c807d3d9a7e592fe6307c363eec028754---\\n' -m - -o - | formail -s ~/mutt/mutt-pipe.sh<enter><untag-pattern>~T<enter>"
This pipes all tagged messages into b4 to collect any tags therein and
has it write an mbox to stdout, which is then exploded using formail and
fed into a script that adds it to a quilt series.
Typical usage for me would be to tag a thread using esc-t, possibly
untag some of the later patches and press 'B' to siphon the selected
patches into quilt.
An obvious alternative for the more git centric folks would be to modify
the above into something using b4 shazam.
prev parent reply other threads:[~2022-12-20 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 21:37 b4 v0.11.0 available Konstantin Ryabitsev
2022-12-20 20:40 ` Peter Zijlstra [this message]
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=Y6IdqeOfLMrBrFiL@hirez.programming.kicks-ass.net \
--to=peterz@infradead.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).