Quoth Robert Graf-Waczenski <mailto:firstname.lastname@example.org>:
> We have been using VSS for almost seven years now and the repository
> appears stable and consistent but has grown beyond 7 GB now mostly
> due to our habit of creating branches with physical repository copies
> which are of course *not* cheap and therefore occupy lots of physical
> space - one major reason to think about migrating to svn.
> The currently available migration tools create a dump file that i can
> import to subversion, potentially piped and filtered via
> Is there any chance to achieve the structure sketched above (with the
> "trunk" and "branches" subfolders below each component's own folder
> and with branches created as correct svn cheap copies) and still have
> the same history information that we have in VSS?
> Or do we have to create the subversion repository in a folder
> structure that is initially identical to what we had in VSS and then
> move stuff around?
Unless you write something that'll manipulate the dump file for you, any
migration tool will most likely produce a dump that contains expensive
copies, same as your original VSS repository. (VSS doesn't know the
difference, so it can't tell the migration tool.)
So if you really want the history and branches retained (and you don't
feel comfortable writing your own migration logic to tweak the dump
file), then you'll need to manually set up your v1 structure, import
that, then copy over to a branch, replace with v2 code, commit, copy to
branch, etc. Fairly time consuming and error prone, I'd imagine.
When we switched to Subversion we essentially just stuck a peg in the
sand, and imported only the current revision of the source. So now we
can only look up to a certain point in the SVN history; beyond that we
have to fire up VSS and look at the history in there instead. But we
haven't needed to do that very often, so it wasn't much of a hardship.
It also provided us the opportunity to refrain from importing some of
the accompanying cruft (old projects and experimental stuff) from the
old server :)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Sep 14 05:21:57 2006