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

cvs2svn.py vs. repository structure

From: Adrian Robert <arobert_at_cogsci.ucsd.edu>
Date: 2004-02-11 16:57:21 CET

> The 'generally accepted' SVN repository has trunk/ branches/ and tags/
> directories at it's root.

I'm only just starting out with svn (but have used cvs for a while),
but it seems like the alternate organization of



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?

Also, does anyone have experience with both kinds of structures and can
speak for or against (pointers to old mailing list threads also welcome
;-| )?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 11 17:24:56 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.