Are people actively working on accomodating branches and tags with
cvs2svn, and if so when will such a feature be available?
I have used svn at home and casually at work since about 0.14, and
finally have an opportunity to move my entire software team into the
light. Until now we have used cvs and wrestled with the branch
dependency misfeatures as best we could, so moving our code base from
cvs into svn is not currently possible with cvs2svn.
I realize that since copies are cheap, branches and tags equate to
copies, so it's not a trivial deal (presumably the admin would need to
be queried as to where to put a cvs branch or tag, and what to call it
in svn), but the alternative is to convert large amounts of my
repository by hand, or leave legacy systems in CVS. Also, it's not
clear from the cvs2svn.py descriptions if it is possible to convert
individual cvs modules in a repository, or if the CVSROOT/modules file
will be considered in the future.
I'm imagining cvs2svn scrubbing for branch and tag names (and module
dependencies?) and then dumping a name-mapping file that could be a
list of "cvsidentifier:somedefaultdestinationURL" might work (possibly
alongside rename and copy hypotheses). As an admin I could then go in
and change the URL destinations as appropriate for the repository into
which I'm introducing things, and then run cvs2svn again feeding it my
new file to get things put where I want them. Any thoughts? Ideally by
adding enough information to the process as an admin I can make
explicit in the svn history dependencies and system configurations that
were implicit (or on 3M notes) with cvs.
Having any cvs2svn tool will only accelerate the mass exodus from the
realm of Perdition devoted to cvs users. Thanks for making it available.
hamilton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 9 21:06:16 2004