Scott Palmer wrote:
> Actually there is no way to do a 1:1 mapping from VSS to subversion.
> So there are some things to be aware of (the term fear is perhaps a
> bit too strong). Subversion has no concept of "sharing" (like
> branching, but updates in any branch affect the other branches as
> well). Subversion does not preserve file modification times.
> Something different needs to be done to handle "labels", etc.
As the author of vss2svn, I'm very well aware of the differences in the
two systems. However, the discussion was on wedged repositories and data
loss, not workflow. The author to whom I originally responded was
implying that converting a repository from VSS to Subversion will make
that repository more prone to becoming wedged. That is absolutely false.
Now, if someone's workflow depends heavily on shared files and the like
in VSS, they will indeed need to come up with a new way of working in
Subversion to get around its lack of such a concept. My team rarely used
labels and shares much, so for us the conversion was rather
straightforward. For others it is much more difficult, and maybe trying
to convert their old repository is too much of a headache.
I simply don't want anyone to base their decision on whether to try to
convert their old history (the ability to do this being a major factor
in some groups' decisions on whether to even use Subversoin at all) on
the misinformation that this might somehow make them more likely to
encounter data errors later on.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 17 23:07:40 2004