On Mon, Mar 03, 2025 at 04:00:39PM +0100, Carlos Maiolino wrote: > This is pretty much aligned with my intentions, I haven't looked close yet how > other subsystems deals with it, but by a few releases now, I keep a > xfs-fixes-$ver branch which I collect patches for the current version, so adding > a new branch for the next merge window is what I aimed to do with > xfs-6.15-merge. > > The question for me now lies exactly on how to synchronize both. You partially > answered my question, although merging the current into next sounds weird to me. for-next really is the convention for what goes into linux-next. For dma-mapping I kept a separate for-linus instead of merging the current one into for-next which also works, but you still might have to merge them occasionally. > > If I merge current into next, and send Linus a PR for each (let's say for -rc7 > and in sequence for the next merge window), Linus will receive two PRs with > possibly the same patches, and yet, on the merge window PR, there will also be a > merge commit from -current, is this what you're describing? Yes, but only if you really need the merge because the code for the next merge window requires it to base new patches onto it. If the merge is a no-op you don't need to merge, and if it is not required for code added Linus prefers to to the merge himself, possible with a little bit of guidance.
