Re: [GIT PULL] KEYS: keys-next-7.1-rc1
Linus Torvalds <[email protected]> Sun, 19 Apr 2026 14:52:06 -0700
| Newsgroups | org.kernel.vger.keyrings,org.kernel.vger.linux-integrity |
|---|---|
| Message-ID | <CAHk-=wjaGOBCsRpEhmPLcsuK6ggiaaeyz0rT6x3Zv7DMK7JNHA@mail.gmail.com> |
On Sun, 19 Apr 2026 at 14:38, Jarkko Sakkinen <[email protected]> wrote: > > I tested both PRs for the same baseline with two separate buildroot builds of You threw away any and all testing that had been done by anybody else in linux-next. And you rebased things on top of a random commit-of-the-day during the merge window, when things are possibly unstable due to all the *other* churn going on. In other words, you did *EVERYTHING* that you shouldn't be doing, and that the documentation tells you not to do. The WHOLE POINT of being in linux-next and being ready when the merge window opens is gone. All for apparently nothing. Those stable cc tags do not add *any* value, since you could just have cc'd stable later instead. I'm not pulling this. You need to stop doing this pointless churn, and read the docs on rebasing. See Documentation/maintainer/rebasing-and-merging.rst about how you are *not* supposed to randomly just rebase, and _particularly_ not rebase on top of some random state during the merge window. Linus