> > Good thing, but it wont always be possible to update Piper code. Or are > > you willing to delay Overflow cvs commits\releases in order to allow > > syncing? > > I could give a notice when I break source compatibility in the Overflow > CVS? That way those you want to update Piper can do so and those who > want to be able to build Piper just don't update Overflow until Piper > supports the changes. Would that be enough? A little more would be nice, dont completely stick to your 'own' codebase. Like the recent update of Overflow I updated Piper so it could compile with the cvs Overflow again. Thee kinda work can be done by everybode, including you. I'm saying that in general it's a good thing that we do some more work on 'other people's' work. Currently the layers and people relation is too much 1-on-1. Dont get me wrong, I know it whould take a long time to work on code you didn't write, and that we all are very buzy. jarl