Re: Is there a way to require an update before commit?

On Mar 2, 2005, at 2:55 PM, Medcoff, Charles wrote:

> I have a bunch of former ClearCase UCM users. ClearCase UCM forces a
> separate branch for each developer and forces one to merge with the
> "trunk"
> when "delivering" changes to the trunk (known in ClearCase UCM as the
> integration stream).
>
> These guys expect the tool to enforce an update before a commit so
> that they
> don't accidently overwrite some else's changes.
>

The Subversion repository won't let anyone overwrite anyone's changes.
If such an attempt is made, the user will get a big error saying their
workspace is "out of date". The user will then be forced to update and
deal with merging changes.

See chapter 2 in the book, "basic concepts", to see diagrams about how
the copy-modify-merge model works. Those diagrams would be good to
show to your users too.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 2 22:07:27 2005