goran
may I suggest you that we do it step  wise :). Because I'm what code 
rot means.
Do not submit one after the other ones, just send one, shout for review 
and test
ten proceed. There are still some KCP items pending and they are roting 
out there too.
So it is much better that we do it in a concerted fashion. So review 
the KCP items and I will
review the cleanup-gk.

But then we should pay attention that doug does not get flooded by 
changes.
Because we increase the conflicting probability.

Stef

On 23 févr. 04, at 08:53, goran.krampe at bluefish.se wrote:

> Hi Doug and all!
>
> As you might have seen I am slowly working my way through Adam's
> cleanup.sar.
> I have no idea how long it will take.
>
> I have submitted the first .cs intended for the update stream -
> SoundSystemCleanup-gk, and I will call all these BlaBlaCleanup-gk. That
> one covers the first (alphabetically) 2 changesets inside Cleanup.sar
> and they have been extensively refined :) including fixing bitrot and
> adding class comments etc.
>
> Of course, it needs testing!!! :) - I haven't even tried filing it into
> a clean 3.7alpha yet.
>
> Anyway, I am a little curious about alpha->beta etc. since Cleanup.sar
> contains reorganisations and refactorings that typically aren't beta
> stuff, but rather alpha.
>
> regards, Göran
>