From: Francois Romieu <[EMAIL PROTECTED]> Date: Wed, 20 Feb 2008 23:40:53 +0100
> David Miller <[EMAIL PROTECTED]> : > [...] > > Because it forces me to pull Linus's upstream into net-2.6, > > I don't have any choice in the matter. > > Jeff's choice is a bit surprizing. That being said, it would had been nice > to fast-forward net-2.6 from a442585952f137bd4cdb1f2f3166e4157d383b82 > to Linus's upstream before applying the content of > 12aa343add3eced38a44bdb612b35fdf634d918c in order to keep the drift > with Linus's branch to a minimum during the bugfix cycle. Keep in mind there are also pending fixes in my net-2.6 tree which Linus hasn't pulled in yet as well. I watch Linus's tree closely, and I'll see any potential merge issue long before it matters, and I always double check before pushing stuff out to him. My job as tree master is to deal with all the merge hassles, should they occur. But up until now everything networking has gone through my tree and everything is fine. The net-2.6 tree isn't even a week old. I planned to pull Linus's tree in right before I leave for a short trip tomorrow afternoon. I'm really not being allowed to make that choice by how these changes are being merged to me. Heck, Jeff even thanked me for making my net-2.6 tree stable and not rebasing, so his method of merging this stuff is doubly surprising for me. Jeff, I really don't want to pull that tree in. Please trust me as your upstream to handle merging issues, as needed. Thanks! -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
