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

Up-to-date-check on commit.

From: Josef Wolf <jw_at_raven.inka.de>
Date: 2002-06-19 21:54:47 CEST


On commit svn makes up-to-date-checks only to locally modified
files/properties. What is the rationale for this? IMHO this is
error-prone. Example:

 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

Let's assume the changes Bob and Joe made are inconsistent. In this
case Sam would ship a broken version. I would suggest, that Joe would
be warned about the fact that foo.c in his WC is no longer up to date.

"svn up"ing just before "svn ci" will not help, because it is not
atomic. There is always the risk that somebody else will "svn ci" just
right after your "svn up".

The current behavior to make the up-to-date-check only for modified
files should IMHO be available only if you give svn some sort of
--force option.


-- Josef Wolf -- jw@raven.inka.de --
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 19 21:55:53 2002

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