[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210322171636.fkep2lby6gnve4su@chatter.i7.local>
Date: Mon, 22 Mar 2021 13:16:36 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
ksummit-discuss@...ts.linuxfoundation.org,
workflows@...r.kernel.org
Subject: Re: RFC: create mailing list "linux-issues" focussed on issues/bugs
and regressions
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 lore.kernel.org regardless of
the list/feed source" capability that may make it unnecessary to create a
separate list for this purpose. There's active ongoing work in the
public-inbox project to provide parallel ways to follow aggregate topics,
including query-based subscriptions (i.e. "put a thread into my inbox whenever
someone mentions my favourite file/function/device name"). This work is not
complete yet, but I have great hopes that it will become available in the next
little while.
Once we have this ability, we should be able to plug in multiple sources
beyond just mailing lists, including a feed of all bugzilla.kernel.org
changes. 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.
-K
Powered by blists - more mailing lists