Kernel SCM saga..
benh at kernel.crashing.org
Thu Apr 7 10:13:08 EST 2005
On Wed, 2005-04-06 at 19:33 -0400, Dan Malek wrote:
> On Apr 6, 2005, at 6:37 PM, Wolfgang Denk wrote:
> > are there any plans yet how to continue PPC kernel development now
> > that Linus (and probably others, too) stopped using BitKeeper?
> For all practical purposes, we have stopped using it as intended long
> ago. When we first started, those of us responsible for maintaining
> of the sources simply continuously pushed updates. Very efficient,
> saw what was up to date. Since 2.4, we have all been passing patches
> around, pushing things into BK didn't seem to matter, and usually
> were ignored or lost. People responsible for certain areas of
> are now just bypassed with sometimes bad patches just given to Andrew
> directly. We may as well go back to using CVS and passing patches
> around, since it easier to do that than the way we have been using BK.
The problem is that we used to have our "own" tree which ended up beeing
a grab bag for all the crap on earth and would drift from upstream in
We are now working much more directly with upstream, and it's not about
random people sending random patches to akpm, for most arch patches,
andrew is actually asking us (or rather paulus) whether to accept or not
the patch. It does sometimes slip through but that's minimal.
If you feel that your stuff isn't properly going upstream in time, then
maybe that is because you aren't sending the patch to the right person
or putting it in the right place ?
All patches posted to linuxppc-dev and linuxppc64-dev are tracked by an
automatic system. They may take some time to go upstream, but they are
More information about the Linuxppc-embedded