Re: linux-distros list policy and Linux kernel

[Greg KH <greg () kroah com>]

On Tue, May 24, 2022 at 06:25:50PM +0200, Mickaël Salaün wrote:
> On 23/05/2022 08:34, Greg KH wrote:
> > On Sun, May 22, 2022 at 08:55:50PM +0100, Sam James wrote:
> > > I'd also like to ask that the final commit messages please reference any
> > > relevant CVEs or at least the security impact. There've been a fair number
> > > of incidents where such information is stripped and it makes tracking
> > > issues *really* hard.
> >
> > That is pretty much impossible and goes against the whole goal of "get
> > this fixed and in a public tree and only tell the world that it was an
> > issue after-the-fact" way that the kernel team works.  If we put all of
> > that in the commit to start with, the whole world knows this info.  We
> > can't go back in time and change git commits for obvious reasons.
>
> It would work well if (as asked Vegard) sources/patches and binaries were
> released simultaneously by both upstream and distributions.

As stated way back at the beginning of this thread, that's impossible to
do, sorry.  And is not the issue here.

greg k-h