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

Re: Up-to-date-check on commit.

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-06-19 22:03:42 CEST

Josef Wolf <jw@raven.inka.de> writes:

> Hello!
>
> On commit svn makes up-to-date-checks only to locally modified
> files/properties. What is the rationale for this?

Josef, you're calling into question the core model of how CVS and
Subversion both work... the so-called "concurrent" versioning model.

This system is the natural result of not having a "lock-modify-unlock"
model. It depends on developers *communicating* with one another.

> 1. Bob$ svn co ; cd wc
> 2. Joe$ svn co ; cd wc
> 3. Bob$ emacs foo.c ; make regression-tests ; svn ci
> 4. Joe$ emacs bar.c ; make regression-tests ; svn ci
> 5. Sam$ svn export; tar czvf foo.tgz wc; cdrecord foo.tgz

If Sam releases a tarball without telling Joe, this is problem with
programmers, not with Subversion. :-)

I'd suggest you read this part of the Design document:

  http://subversion.tigris.org/files/documents/15/17/svn-design.html

Take a look at the section labeled "Subversion Does Not Lock Files".

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 19 22:05:36 2002

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