tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Rob Herring <robh@kernel.org>,
	users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.3.4 released
Date: Fri, 27 Mar 2020 14:15:26 -0400	[thread overview]
Message-ID: <20200327181526.e46zqg4bne2rplbm@chatter.i7.local> (raw)
In-Reply-To: <CAHmME9oP4epS5UvrrnvLDcSEZAHXgrrGHkbZ7ddryKO56KFosg@mail.gmail.com>

On Thu, Mar 26, 2020 at 02:18:26PM -0600, Jason A. Donenfeld wrote:
> Looks like the auto project detection has issues:

It's not really auto-project detection. We use public-inbox itself to 
look for "any list where this message-id shows up". Currently, it does 
no thread completion matching and there is no way to set preference. I 
hope that we'll be able to implement these features in the future.

For now, I plan to use the following approach:

- when a thread is incomplete, look at other mailing lists where it was 
  sent (in to: and cc:)
- grab https://lore.kernel.org/lists.txt
- try to see if we have archives for any of those other lists
- try to backfill missing messages from other lists

This is not great, but it should hopefully help with this problem until 
public-inbox gains ability to return a thread collected from multiple 
lists (it should be able to do that once cross-list search becomes 
available).

> (Also: lore still calls linux-kernel "lkml" which is a bit confusing.)

I know, and I'll have some mechanism in place so both work soon.

-K

  reply	other threads:[~2020-03-27 18:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 22:20 b4 v0.3.4 released Konstantin Ryabitsev
2020-03-25  2:11 ` [kernel.org users] " Jason A. Donenfeld
2020-03-25  2:19   ` Jason A. Donenfeld
2020-03-25 15:05     ` Konstantin Ryabitsev
2020-03-25 15:26   ` Konstantin Ryabitsev
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11   ` Rob Herring
2020-03-26 16:16     ` Konstantin Ryabitsev
2020-03-26 16:27       ` James Bottomley
2020-03-26 16:31         ` Geert Uytterhoeven
     [not found]     ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32       ` Konstantin Ryabitsev
2020-03-26 20:18         ` Jason A. Donenfeld
2020-03-27 18:15           ` Konstantin Ryabitsev [this message]
2020-04-06 21:53           ` Konstantin Ryabitsev
2020-09-22 22:17         ` Rob Herring

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=20200327181526.e46zqg4bne2rplbm@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --cc=robh@kernel.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).