[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: cvs2svn.py vs. repository structure

From: <kfogel_at_collab.net>
Date: 2004-02-12 16:30:37 CET

Adrian Robert <arobert@cogsci.ucsd.edu> writes:
> I'm only just starting out with svn (but have used cvs for a while),
> but it seems like the alternate organization of
> project1
> trunk
> tags
> branches
> project2
> trunk
> ...
> has its advantages as well, for repositories with multiple, partially
> related modules. It helps avoid namespace clashes if you like to
> branch and tag different projects independently, and you can always
> add a 'global_tags' top-level directory if you want to tag more than
> one project in an integrated release (and likewise 'global_branches').
> Anyone know how hard it would be to update cvs2svn to do this
> (optionally), or does one of the other cvs conversion tools do it?

I don't know how hard that would be -- not completely trivial, at
least, due to the way tag and branch creation is done in cvs2svn. I'd
be very reluctant to try to integrate right now. Let's get the bugs
fixed in the current, one-layout-choice implementation, then look at
adding options.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 12 17:32:33 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.