Re: [MAINTAINERS SUMMIT] The amount of -stable emails

["Theodore Ts'o" <tytso@mit.edu>]

On Wed, Aug 06, 2025 at 01:24:47PM +0100, Mark Brown wrote:
> On Wed, Aug 06, 2025 at 08:20:02AM -0400, Sasha Levin wrote:
> > On Wed, Aug 06, 2025 at 11:42:03AM +0100, Mark Brown wrote:
> 
> > > TBH I think a summary would help there - currently you're looking at six
> > > threads for all the different stables and have to check every patch in
> > > each, if we were instead getting a summary that says that patch A has
> > > been backported to stables X-Y then it'd highlight more clearly if
> > > something wasn't pulled far enough back.
> 
> > Something along the lines of
> > https://lore.kernel.org/all/20250805130945.471732-1-sashal@kernel.org/ ?
> 
> Yes.  Possibly also putting the range in the body in case people find
> that more visible when reading the thread?

This is a bit of a tangent, but something that I think would be
*really* cool is if there was a web dashboard which displayed commits
that were either (a) tagged with a Fixes: or cc: stable, (b)
explicitly requested by a maintainer / developer, (c) backported
because it was a dependency needed for (a) or (b), and showed links to
commits to the LTS links where it was a backported, and optionally a
link to the "couldn't backport automatically" e-mail if it couldn't be
backported.  It would also be useful if dashboard reported whether
there was a CVE associated with the commit.

The dashboard should be searchable by subsystem, and/or by date or
kernel version range.  And it would be nice if maintainers could
subscribe to periodic update e-mails on a per-subsystem basis.

If we think this would be useful, perhaps we could try to see if we
could get LF funding/support to create such a developer tool?

      	     		     	       	    - Ted