Workflows Archive on
 help / color / Atom feed
From: Konstantin Ryabitsev <>
To: Rob Herring <>
Cc: Kevin Hilman <>,
Subject: Re: get-lore-mbox: quickly grab full threads from lore
Date: Mon, 24 Feb 2020 13:10:42 -0500
Message-ID: <20200224181042.h4q3umrjqxujkxwt@chatter.i7.local> (raw)
In-Reply-To: <>

On Mon, Feb 24, 2020 at 11:39:02AM -0600, Rob Herring wrote:
> It may be easy enough unless you have something like this series:
> It backtraces if you give it patch 2 msgid:
> Presumably because patch 2 and and the cover letter aren't on the same
> list? Arguably, that's bad practice, but it's quite common to only
> have 1 or a few patches of the whole series. If you start with the
> cover letter, then it can find everything.

There is currently no way to reconstitute a single thread from multiple 
sources -- this is something that we would like to change in the near 
future. If a message is sent to multiple mailing lists, then there is no 
guarantee from which list you are going to get the thread, unless you 
specify -p projname. E.g.:

./ -o/tmp -a -p linux-doc \

However, this will only pick up follow-ups from linux-doc, so if there 
are any trailers sent to another list, get-lore-mbox will know nothing 
about them:

> Also, it didn't pick up 2 out of 3 Acked/Reviewed-by tags:

Changing this behaviour requires significant rewrites of the backend in 
order to be able to mux results from different sources. This is work 
that is planned and will be happening.

For the moment, I don't have any good solutions other than fixing the 
backtrace (which is now fixed).


  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
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 [this message]
2020-02-15 22:23 ` mbox-export-patch, notmuch-export-patch Sean Whitton

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:

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

  git send-email \
    --in-reply-to=20200224181042.h4q3umrjqxujkxwt@chatter.i7.local \ \ \ \ \

* 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