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

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

From: Medcoff, Charles <Charles.Medcoff_at_gedas.com>
Date: 2005-03-03 15:58:21 CET

Yes you and many others that pointed this out are correct. I guess it
slipped my mind - In fact I should have known this as I've pretty much read
the subversion book cover to cover - I guess it slipped my mind.

One of our developers must have overwrote some changes to a file while
editing a conflict and I too quickly jumped to the wrong conclusion in the
heat of the moment.

Thanks for pointing out my error.

-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Wednesday, March 02, 2005 4:02 PM
To: Medcoff, Charles
Cc: 'Johan Appelgren'; users@subversion.tigris.org
Subject: RE: Is there a way to require an update before commit?

On Wed, 2005-03-02 at 15:55 -0500, 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
> 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
> don't accidently overwrite some else's changes.

Subversion will already enforce this. If changes have been made and
committed, the WC will be out of date and a new commit will not be

Isn't this sufficient?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 3 16:01:20 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.