On Sat, Feb 24, 2024 at 06:16:24AM +0100, Greg KH wrote:
> On Fri, Feb 23, 2024 at 11:48:49AM -0800, Paul E. McKenney wrote:
> > On Fri, Feb 23, 2024 at 02:15:30PM +0100, Greg KH wrote:
> > > On Wed, Feb 07, 2024 at 07:08:46PM +0800, Zqiang wrote:
> > > > From: Paul E. McKenney <paul...@kernel.org>
> > > >
> > > > commit bc31e6cb27a9334140ff2f0a209d59b08bc0bc8c upstream.
> > >
> > > Again, not a valid commit id :(
> >
> > Apologies! With luck, there will be a valid ID next merge window.
> > This one does not backport cleanly, so we were trying to get ahead of
> > the game. Also, some of the people testing needed the backport due
> > to the usual issues. :-/
> >
> > Any advice to handle this better next time around? (Aside from us
> > avoiding CCing stable too soon...)
>
> You can just wait until it hits Linus's tree, otherwise we do get
> confused :)
>
> Or if you don't want to wait, put it in the notes section below the ---
> line and say "this isn't in Linus's tree yet, the git id mentioned is a
> lie!" or something like that. Give us a chance to figure it out
> please...
Thank you, and should this situation arise in the future, we will put
the disclaimer after the "---", avoid CCing -stable, or similar.
Again, apologies for the hassle!
Thanx, Paul
