Adrian Bunk [off-list ref] writes:
The over 3 weeks old -next already contains mostly the same as the HDLC
tree contains now.
The thing you two should sort out is why the tree ended up as an own
tree in -next instead of pull requests to David long ago.
E.g. the netdev and wireless trees also don't go into -next, but instead
with frequent pull requests to David.
I can't see any problem with this, is there any?
I want the HDLC tree tested in next before it's merged upstream
(= David's tree(s)). I don't want to push crap upstream first and
only then try to fix it (though a bug still slips in sometimes).
--
Krzysztof Halasa
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: Mon, 13 Oct 2008 16:53:17 +0200
Adrian Bunk [off-list ref] writes:
quoted
The over 3 weeks old -next already contains mostly the same as the HDLC
tree contains now.
The thing you two should sort out is why the tree ended up as an own
tree in -next instead of pull requests to David long ago.
E.g. the netdev and wireless trees also don't go into -next, but instead
with frequent pull requests to David.
I can't see any problem with this, is there any?
I want the HDLC tree tested in next before it's merged upstream
(= David's tree(s)). I don't want to push crap upstream first and
only then try to fix it (though a bug still slips in sometimes).
You're supposed to have your changes merged into the relevant
subsystem tree long before Linus's merge window opens up.
That's how it is meant to work.
What I'm doing with networking is nothing special.
So please be punctual and merge early and often to Jeff and
myself, so that you don't miss the merge window in the future.