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

Re: Concurrent versioning = spawn of the devil?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2006-11-09 19:03:12 CET

On Wed, 2006-11-08 at 14:43 -0700, Andy Peters wrote:

> > Subversion, OTOH, by default uses the "Copy-Modify-Merge" pattern,
> > which
> > has some downsides on first glance if you are used to the VSS
> > patterns.
> > With the Subversion pattern, the user is not notified about changes by
> > others until the user *commits* his own changes.
>
> To be completely clear: the user is not notified about changes
> committed by others until after the user attempts to commit his own
> changes. If any changes were made, there's a conflict and the user
> has to resolve it before he's allowed to commit his changes.

Yes, but that's assuming the user doesn't bother to update to
pick up the work done by others during the time while he
is adding these incompatible changes. If that time interval
is large he might have been able to avoid the problem easily.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 9 19:04:40 2006

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