From: Sean Whitton <spwhitton@spwhitton.name>
To: workflows@vger.kernel.org, ~sircmpwn/sr.ht-discuss@lists.sr.ht
Subject: mbox-export-patch, notmuch-export-patch
Date: Sat, 15 Feb 2020 15:23:19 -0700 [thread overview]
Message-ID: <87lfp38p7s.fsf@iris.silentflame.com> (raw)
In-Reply-To: <20200201030105.k6akvbjpmlpcuiky@chatter.i7.local>
Hello,
On Fri 31 Jan 2020 at 10:01PM -05, Konstantin Ryabitsev wrote:
> Hi, all:
>
> I'd like your opinion on this quick helper script I wrote that uses any
> message-id to grab a full thread from lore.kernel.org and save it as a
> mbox file.
>
> What's more useful, it can also prepare a mbox that you can pass
> straight to git-am:
>
> - it will tally up all "Acked-by", "Reviewed-by" etc trailers and add
> them to the proper patch headers
> - it will properly sort patches in the series, so you don't have to do
> it manually
Inspired by some of this functionality, I just uploaded
'mbox-extract-patch' to Debian unstable in the 'mailscripts' package, or
here:
script: https://git.spwhitton.name/mailscripts/tree/mbox-extract-patch
docs: https://git.spwhitton.name/mailscripts/tree/mbox-extract-patch.1.pod
It does what get-lore-mbox.py does except without the kernel-specific
functionality, so it might be interesting for people wanting to use a
git-send-email(1)-based workflow for projects whose mailing lists are
not archived on lore.kernel.org.
mailscripts also contains a wrapper, notmuch-extract-patch, for notmuch
users.
--
Sean Whitton
prev parent reply other threads:[~2020-02-15 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 3:01 get-lore-mbox: quickly grab full threads from lore Konstantin Ryabitsev
2020-02-01 17:43 ` Kees Cook
2020-02-03 22:38 ` Dan Williams
2020-02-14 19:30 ` Kevin Hilman
2020-02-14 19:40 ` Toke Høiland-Jørgensen
2020-02-14 19:53 ` Mark Brown
2020-02-14 19:53 ` Konstantin Ryabitsev
2020-02-14 20:35 ` Kevin Hilman
2020-02-17 10:52 ` Geert Uytterhoeven
2020-02-17 14:30 ` Konstantin Ryabitsev
2020-02-24 17:39 ` Rob Herring
2020-02-24 18:10 ` Konstantin Ryabitsev
2020-02-15 22:23 ` Sean Whitton [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=87lfp38p7s.fsf@iris.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=workflows@vger.kernel.org \
--cc=~sircmpwn/sr.ht-discuss@lists.sr.ht \
/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).