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

Help or suggestions on porting to subversion

From: San Martino <sanmrtn96_at_gmail.com>
Date: Wed, 10 Nov 2010 21:09:59 +0100


we are porting hundreds of projects from an old versioning system to
subversion. We would like to make use of the trunk, tag and branch
For the convertion we used an automatic tool which preserved the
original layout under trunk/ . By looking at the layout, one problem
is that the files of these projects are not semantically grouped into
different directories (one directory for project), but are grouped
according to their extensions (.txt, .dll, etc..) or software in which
they are installed. For example, under trunk we have automatically

Application Server

while /tag and branch/ are empty

There are hundreds of files under each directory. We want to preserve
this layout, since it's basically impossible to reorganize all the
files in projects/directories.
Furthermore, we cannot checkout/update these huge directories whenever
we want to change a single file, for example a single package.
While it will no longer be the same with the new projects (some of
which might depend on old stuff), what we would like to do with the
old stuff is to be able to checkout a small number of single files
semantically representing a project and tag the release or snapshot
under /tag when the changes are done.

How could we do in your opinion?
Received on 2010-11-10 21:10:41 CET

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.