> -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > > Actually, that would be: > > http://svn.apache.org/repos/asf/avalon/ > http://svn.apache.org/repos/asf/avalon/components > http://svn.apache.org/repos/asf/avalon/sandbox > http://svn.apache.org/repos/asf/avalon/site I think we want 4 separate locations:
http://svn.apache.org/repos/asf/avalon/framework (or 'core', or something) http://svn.apache.org/repos/asf/avalon/components http://svn.apache.org/repos/asf/avalon/sandbox http://svn.apache.org/repos/asf/avalon/site but that's not important at the moment. > Think of Subversion as a versioned file system with a DAV interface. One > of > its lovely properties is that when you tell this file system to copy a > file, > the file's history is preserved. So if we have: > > http://svn.apache.org/repos/asf/avalon/excalibur > > and we want to move any or all of it, we just tell Subversion to do that, > and it does it without losing track of any historical information. In > fact, > when you move it, I can still check out an old version from the old > location. The entire virtual file system has history, including moves and > copies. So (sorry if I'm slow here) we would want to migrate excalibur to svn AS IS before attempting and merging of excalibur into avalon-components. That would be fine by me. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
