On Fri, Dec 23, 2022 at 10:10:30PM -0800, Linus Torvalds wrote: > On Fri, Dec 23, 2022 at 9:35 PM Michael S. Tsirkin <m...@redhat.com> wrote: > > > > They were in next-20221220 though. > > So, perfect for the *next* merge window. > > Do you understand what the word "next" means? We don't call it > "linux-this", do we? > > This is not a new rule. Things are supposed to be ready *before* the > merge window (that's what makes it "next", get it?). > > I will also point you to to > > > https://lore.kernel.org/lkml/CAHk-=wj_hcgfznyzhtlj7qc2613zphkdtlh6ndciwopzrfh...@mail.gmail.com/ > > where I'm being pretty damn clear about things. > > And before you start bleating about "I needed more heads up", never > mind that this isn't even a new rule, and never mind what that "next" > word means, let me just point to the 6.1-rc6 notice too: > > > https://lore.kernel.org/lkml/CAHk-=wguzwx8sbb8zvm7fxwvfx6cgue7x+e16vkoql7ok9v...@mail.gmail.com/ > > and if the meaning of "next" has eluded you all these years, maybe it > was high time you learnt. Hmm? > > Linus
Yea I really screwed up with this one. High time I learned that "no fallout from testing" most likely does not mean "no bugs" but instead "you forgot to push to next". Putting procedures in place now to check automatically. -- MST _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization
