you should read the suggestions from people like Pier on infrastructure, and see what he did for cocoon, learn from those experiences. I do agree the repo is too big and it make sense to wipe stuff clean; the current approach your suggesting is somewhat suboptimal IIUC though. Pruning using 'rm' or 'mv' is not good, especially not when using tags and branches.

while we're at it, we should move the current avalon/* to avalon/framework/*.

cheers,

- LSD

Berin Loritsch wrote:
Our Avalon core CVS is currently bloated to roughly 10 times the
size it needs to be.  This is because of legacy stuff in the
repository that we no longer need or even refer to.  I would
like to prune certain directories so that we can have a faster
update time.

These directories should not be in anyone's current workspace,
so removing the directories should not cause any problems.

My plan is to demonstrate the new CVS archive in my user space,
let us vote on it, and archive the cruft in the avalon-site/graveyard.

Are there any objections?



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to