Workflows Archive on
 help / color / Atom feed
From: Kevin Hilman <>
To: Konstantin Ryabitsev <>
Subject: Re: get-lore-mbox: quickly grab full threads from lore
Date: Fri, 14 Feb 2020 12:35:05 -0800
Message-ID: <> (raw)
In-Reply-To: <20200214195318.ghvcroucki4pcz4r@chatter.i7.local>

Konstantin Ryabitsev <> writes:

> On Fri, Feb 14, 2020 at 11:30:42AM -0800, Kevin Hilman wrote:
>> Konstantin Ryabitsev <> writes:
>> > I'd like your opinion on this quick helper script I wrote that uses any 
>> > message-id to grab a full thread from and save it as a 
>> > mbox file.
>> This is very useful, thank you!
>> One question/request: Is there a way for it to only grab a subset of a
>> series?  e.g. Some series contain patches that might end up going
>> through a couple different trees (e.g. DT patches typically take a
>> separate path than drivers) so as a maintainer for one of the
>> subsystems, I might want to only get a subset of the series into an
>> mbox, not the whole thing.
>> IOW, Right now even if I pass a msgid from the middle of the series, it
>> finds the whole series (which is cool!), but what if I want to apply
>> just that single patch?  Or even better, I might want to only apply
>> patches 3-5 and 9 from a 10-patch series.
>> Is this something do-able?
> I think for such cases it's easy enough to just edit the .mbx file to 
> remove the patches you're not interested in.

Yes, that was my first "solution", but it's not very easy to
automate. :)

If there needs to be a manual step, I prefer 'git am --interactive'.

Anyways, this tool is really great and it's already replacing some of my
homebrew scripts.



  reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01  3:01 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 [this message]
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 ` mbox-export-patch, notmuch-export-patch Sean Whitton

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Workflows Archive on

Archives are clonable:
	git clone --mirror workflows/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 workflows workflows/ \
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone