Re: CVS on sourceforge

[Sven L. <lu...@dp...>]

On Tue, May 23, 2000 at 12:42:09PM +0100, Alan Buxey wrote:
> hi,
> 
> > Well, yes, but 2.2 is end of live, so no need to synchronize it with the
> > bitkeeper /whatever tree, it is more an issue of the 2.2 m68k tree (which is
> > no more maintained, because 2.3 works on m68k, ...
> 
> doesnt m68k get 2.2.14 etc then? Or are they [users + developers] all over
> on 2.3.x now ?

m68k has 2.2.10 and 2.3.x ...

> still on LinuxAPUS we are on 2.2.10 with no sight of 2.2.14  (what are the
> issues? At least on sourceforge it'll be easier to keep track of the
> problems via the noticeboard systems)

Well, 2.2.10 is base on 2.2.x/m68k which is stuck at 2.2.10, so there is no
chance of 2.2.x to go further on apus, unless someone takes all the 2.2.x m68k
patches, sort out the amiga related ones from the (atari/mac/whatever ones)
and tries to apply the 2.2.11-15 patches to it.

But the consensus, both from the apus guys (well mostly jesper) anbd the m68k
ones (Jes sorensen) is that it is a waste of resource to try to work on 2.2.x
and are concentrating on 2.3.x.

If you would work on 2.2.10, both for apus and m68k, please contact Jes, he
has some stuff already done ...

> looking forward to the new era...it seems that sourceforge will remove a
> bottleneck by centralising resources...and we can look at 2.3.x ernestly

Well, i think not that it really was a bottle neck, just lack of people
working on it. Lets hope this new structure will help more people to be
involved in kernel developpment.

Friendly,

Sven LUTHER