On Fri, Nov 01, 2024 at 09:22:30AM -0700, Oliver Upton wrote: > On Fri, Nov 01, 2024 at 09:16:42AM -0700, Sean Christopherson wrote: > > One thing I'll add to my workflow would be to do a local merge (and smoke test) > > of linux-next into kvm-x86 next before pushing it out. This isn't the only snafu > > this cycle where such a sanity check would have saved me and others a bit of pain. > Eh, shit happens, that's what -next is for :) > The only point I wanted to make was that it is perfectly fine by me to > spread the workload w/ a topic branch if things blow up sometime after > your changes show up in -next. Yeah, the -next breakage is a bit annoying but so long as it gets fixed promptly it's kind of what it's there for. It's much more of an issue when things make it into mainline, and can be very problematic if it makes it into a tagged -rc (especially -rc1) or something.
Attachment:
signature.asc
Description: PGP signature
