Re: [MAINTAINERS SUMMIT] Hidden commits from next (aka why maintainers hoard them in backpack)

[Vlastimil Babka <vbabka@suse.cz>]

On 9/11/25 16:25, Steven Rostedt wrote:
> On Thu, 11 Sep 2025 14:40:45 +0100
> Mark Brown <broonie@kernel.org> wrote:
> 
> I now have several topic branches, and I try hard to avoid merges as they
> tend to make my pull requests more complex. But every so often, I have a
> patch that comes in that is required for work in two of my existing topic
> branches. This is a case where one change is required for two topic
> branches to continue more work.
> 
> In these rare events, I will apply the change to one of the topic branches,
> then merge it into the other with a detailed explanation to why I needed to
> do that merge.

Could you alternatively put the commit in a shared base of the two topic
branches, and thus avoid the merging? Or it is a case that you don't want to
rebase (at the moment because merge window is near, or ever?), or the change
can't be moved ahead of the other work in those topic branches?

> Linus hasn't complained about it, so I'm guessing that's the correct thing
> to do.
> 
> -- Steve
>