Alan Cox <alan@lxorguk.ukuu.org.uk>:
> > Alan Cox <alan@lxorguk.ukuu.org.uk>:
> > > I have for one. Its definitely the wrong approach to bomb Linus
> > > with patches when doing the merge of an architecture. All the
> > > architecture folk with in their own trees for good reason.
> >
> > On the other hand, Linus has objected to the One-Big-Patch approach in
> > the past with respect to things like the networking and VM code. How
> > are people to know what the right thing is?
>
> Who said anything about one big patch ? Just because you have a lot
> of differences doesnt mean you send Linus one giant splat of code. I
> don't send Linus -ac for example.
OK, so maybe I'm being stupid. But the implication of this talk of separate
port trees and architecture merges is that these guys periodically send big
resync patches to you and Linus.
If that's not what's going on, what is?
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>Never could an increase of comfort or security be a sufficient good to be bought at the price of liberty. -- Hillaire Belloc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 23 2001 - 21:00:36 EST