Workflows Archive on
 help / color / Atom feed
From: Thorsten Leemhuis <>
To: Eric Wong <>,
	James Bottomley <>
Cc: Konstantin Ryabitsev <>,,
	Greg KH <>,,
Subject: Re: RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions
Date: Mon, 22 Mar 2021 19:55:29 +0100
Message-ID: <> (raw)
In-Reply-To: <20210322183427.GA1195@dcvr>

On 22.03.21 19:34, Eric Wong wrote:
> James Bottomley <> wrote:
>> On Mon, 2021-03-22 at 13:16 -0400, Konstantin Ryabitsev wrote:
>>> On Mon, Mar 22, 2021 at 04:18:14PM +0100, Thorsten Leemhuis wrote:
>>>> Note, there is a second reason why ksummit-discuss is CCed: another
>>>> reason why I want to create this new list is making it easier to
>>>> find and track regressions reported to our various mailing lists
>>>> (often without LKML in CC, as for some subsystems it's seems to be
>>>> custom to not CC it). 
>>> FYI, there will soon be a unified "search all of
>>> regardless of the list/feed source" capability

Ahh, nice, thx to everyone working on that!

> [...]
>>> Once we have this ability, we should be able to plug in multiple
>>> sources beyond just mailing lists, including a feed of all
>>> changes.

Out of curiosity: will that work for other bug trackers as well? Like
the gitlab instance used by the drm developers? It's not really
important and I guess the answer will be "no", but the question came up
while at it...

>>> This should allow someone an easy way to
>>> query specific bugs and may not require the creation of a separate
>>> list.
>>> I'm not opposed to the creation of a new list, of course -- just want
>>> to make sure it's aligned with the improvements we are working to
>>> make available.
>> I suspect the problem is that there's no known useful search string to
>> find a bug report even given a searchable set of lists,

Exactly. Due to my work on reporting-issues.rst I try to look at it from
the users point of view. And they currently have no easy way to search
for existing reports without getting lots of other stuff mixed into the
results they are not interested in. That makes it hard. :-/

>> so the main
>> purpose of this list would be "if it's on here, it's a bug report" and
>> the triage team

If one exists ;-)

>> can cc additional lists as appropriate.  Then we simply
>> tell everyone to send kernel bugs to this list and ask maintainers to
>> cc it if a bug report shows up on their list?
> It seems having "bug" or "regression" in the subject could be sufficient?
> "s:Regression" or "s:Bug" can be used to query messages reasonably
> quickly:

Could, but I fear it might fail, as modifying the subject is a little
unusual to the normal working style; but "adding people and appropriate
mailing lists to the CC" OTOH is something that people do every day.

And that's why I still think having a separate list is the best idea.
But using tags is totally fine for me, if that the general consensus.

Ciao, Thorsten

  reply index

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 15:18 Thorsten Leemhuis
2021-03-22 16:55 ` [Ksummit-discuss] " Lukas Bulwahn
2021-03-22 19:49   ` Thorsten Leemhuis
2021-03-22 17:16 ` Konstantin Ryabitsev
2021-03-22 17:57   ` [Ksummit-discuss] " James Bottomley
2021-03-22 18:34     ` Eric Wong
2021-03-22 18:55       ` Thorsten Leemhuis [this message]
2021-03-22 19:20         ` Konstantin Ryabitsev
2021-03-22 18:32 ` Linus Torvalds
2021-03-22 19:25   ` Thorsten Leemhuis
2021-03-22 21:56     ` [Ksummit-discuss] " Theodore Ts'o
2021-03-23  8:57       ` Thorsten Leemhuis
2021-03-23 15:01         ` Konstantin Ryabitsev
2021-03-23 19:09           ` Thorsten Leemhuis
2021-03-23 18:11         ` Theodore Ts'o
2021-03-23 18:51           ` Thorsten Leemhuis
2021-03-23 14:57     ` Luis Chamberlain
2021-03-23 16:20     ` Steven Rostedt
2021-03-23 16:30       ` [Ksummit-discuss] " James Bottomley
2021-03-23 21:43         ` Konstantin Ryabitsev
2021-03-23 23:11           ` Eric Wong
2021-03-23 18:07       ` Theodore Ts'o

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 \ \ \ \ \ \ \ \ \ \

* 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