Elliott Mitchell

There wouldn't be much difference. Simply duplicates everything for 6.6. If this got approved quickly it _might_ go in before #14868.

Just as long as the order of operations isn't. What is really needed is opinions on which options should really be copied from `generic`. Rather a lot of those don't...

I guess we could almost simply dump `generic`. The extra settings in `generic` are likely rarely used on non-amd64, whereas the late-model P4s _should_ be on `64`. Any comments on...

Hmm, unsure why I deleted the branch. Perhaps didn't want markers hanging around in `git`, and goofed on which one #14944 was tied to. Automatically closing pull requests isn't helpful.

The more I look at this, the more I'm favoring simply deleting "generic" instead of merging it into "legacy". The reason being "generic" has too many settings appropriate for a...

Not having such a device, so merely commenting as an on-looker. Is it really worthwhile to add 6.1 _and_ 6.6? Might it make more sense to add 6.6 and completely...

Seemed like there was hope the next release would use 6.6, in which case skipping 6.1 might be better. Enough commentary from the peanut gallery on this though.

I see issues to point to in a review. I was rather hoping someone would at least _test_ #14907 before I submit a review of #14913. Someone who cannot review...

I am unsure I've quite replicated `kernel_bump.sh`'s functionality _exactly_, but I am fairly confident I've got something which is mostly compatible based on invoking `kernel_upgrade.pl` from #14907.

...and elsewhere people were complaining about frequent rebases... > BTW, @oliv3r there is now a discussion on the IRC regarding the issue that doing remove and then adding stuff later-in...