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

Re: Subversion vs CVS for document files

From: Thomas Harold <tgh_at_tgharold.com>
Date: 2006-11-17 04:04:12 CET

Robert Graf-Waczenski wrote:
> Ah, VSS bashing! Can't resist to join...
> VSS, by design, depends heavily on well-synchronized system clocks of all
> client computers performing checkins. In the worst case, your VSS database
> is trashed completely simply because one computer checks in a change while
> his system clock is on a time *before the VSS project was created*. The main
> lesson to learn from this is: You can simply not trust the VSS history
> because all timestamps reflected in the history stem from the system clock
> that the client computer had when the checkin was executed.
> The MSDN says to this: "Make sure that you synchronize the dates and system
> clocks for all Visual SourceSafe client computers".

Interesting, I hadn't paid attention to that.

However, we had good luck using VSS for 6 years for 5 developers prior
to switching over to SVN.

Our secret? We only accessed VSS via SourceOffSite, a 3rd party tool
suited for WAN access which ran on the same server as the VSS
repository. Basically we did an end-run around the common cause of VSS
corruption issues.

(Even with all that, I still couldn't get vss2svn working... so we just
left VSS+SOS in place for historical purposes and loaded the current
revision of everything into SVN.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 04:04:44 2006

This is an archived mail posted to the Subversion Users mailing list.