Re: linux-next: tip-core merge conflict

Ingo Molnar
2008-06-12T14:10:41Z

* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> > I have dropped the offending commit from kbuild.git for now. It will
> > be applied late in the merge window.
>
> OK, thanks. However, I am more than happy to carry these trivial
> merge fixes (and Linus does these fixes all the time) so if you want
> to keep this sort of thing in your tree, that's OK. The reason I
> report them is that I try to report everything.

i think it might be a communications issue - as conflicts are not a
problem per se, they are just a complication that you resolve.

So it might make sense to change the subject line of your merge
resolution mails from:

linux-next: tip-core merge conflict

to:

linux-next: manual merge of tip-core

that way people still stay informed about interactions between trees
(and can reduce them when they are avoidable, and can check the result
as well since it was done manually), but dont see it as some sort of
failure that needs to be 'resolved' via dropping patches.

Ingo