> -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > > I believe that due to the way in which Avalon wants to re-organize and > re-factor the code, it is absolutely imperative that we switch to > Subversion > promptly. Otherwise we will shortly have a code base where the active > code > has been completely disassociated from its development history. > > I don't believe that I can possibly get across how totally unacceptable I > find the current situation.
If subversion solves this problem, then I'm +1 for the switch. Noel, What all would be involved in moving to svn? I think in the end we would like to just have: avalon avalon-components avalon-sandbox avalon-site Would we need to temporarily move excalibur into svn and then into avalon-components, or could we keep excalibur in CVS and then move from there directly into avalon-components (in svn) while still preserving revision history? (I hope I'm being clear) J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
