Hi Linus, On Wed, 16 Mar 2016 10:18:33 -0700 Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > > > I fixed it up (see below) and can carry the fix as necessary (no action > > is required). > > Side note: can you change this wording for your manual merge script? > Last merge window (or was it the one before it?) we had confusion with > people who thought that "no action is required" means "you can just > ignore this entirely". > > I want people who have known merge issues to at the very least > *mention* them to me when they send the pull request, and I also think > that trees that have merge conflicts that aren't just totally trivial > should also make sure that they have communicated with each other > about why the problem happened. > > This is *particularly* true for the complete effing disaster that is > mellanox and rdma-vs-networking. > > So please don't say "no action is required". Please make it clear that > there may not be any further action needed for linux-next itself, but > that other action may certainly be required. Yeah, I can see your point. The "no action required" was a reaction to people going off and rebasing their tree or dropping patches at any sign of a conflict at all. How about "This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may want also want to consider cooperate with the maintainer of the conflicting tree to minimise any particularly complex conflicts." -- Cheers, Stephen Rothwell -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
