On Sep 17, 2004, at 5:07 PM, Toby Johnson wrote:
> 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.
Right. I was referring to the idea that simply converting a database
from one system to another isn't necessarily so straightforward. We
have elected not to do the conversion, simply because it doesn't seem
to make sense to munge the data into a new format for the purpose of
preserving the historical information which is already preserved just
fine where it is.
> 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.
Got it. Though failure to be aware that 'sharing' didn't get converted
could cause some problems later on :) - though that would be the fault
of the user, not the software.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 18 03:28:04 2004