> If subversion solves this problem, then I'm +1 for the switch.
It does. You have to copy and rename the files using Subversion, so that it
can track the operation.
> What all would be involved in moving to svn?
Request to infrastructure, who would do the CVS to SVN conversion. One of
the things we might want to resolve at that time would be repairing (if
possible) some of the disassociations we have already done. But the experts
don't include me. :-) They do, however, include Greg, Justin, Sander and
Fitz.
[As a side note, since it does not exist in the current code, I was
commenting last night that I thought it would be very cool if a future
enhancement to cvs2svn used a variation of Eric Raymond's shred-based
comparator to help detect and repair disassociations.]
> I think in the end we would like to just have:
> avalon
> avalon-components
> avalon-sandbox
> avalon-site
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
But you can reorganize it however you want, once the content is present.
> 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?
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.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
