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

Re: Atomic updates

From: Paul Koning <pkoning_at_equallogic.com>
Date: 2005-11-23 21:06:59 CET

>>>>> "Erik" == Erik Huelsmann <ehuels@gmail.com> writes:

>> > You can do this today. Get the head revision number, then do an
>> svn > update -r <that rev>
>> >
>> > That's what I use when I want an "atomic" update (or checkout)
>> that is > done in several parts (several svn commands)
>> >
>> > paul

>> Does it have any other advantage than guaranteeing that you will
>> not get a mix of files from different svn revnums because HEAD
>> changed while you performed the update in several steps?

 Erik> NO NO NO!!!!!

 Erik> Please don't suggest that's possible with Subversion! That's a
 Erik> problem with CVS which we have solved!

 Erik> If you run 'svn up' your working copy is updated to *the
 Erik> revision which is HEAD at the moment your update starts*. This
 Erik> means a new revision may become HEAD in the mean time, but the
 Erik> changes will not be sent to your working copy.

 Erik> In other words: If revision 3 is HEAD when you run svn up, if
 Erik> revision 4 is committed while you run your update, your working
 Erik> copy will be at revision 3 and *not* partly at revision 4.

Correct, but you missed something. I said "in several steps".

What you describe is indeed a CVS problem that SVN fixed, when you do
an update or checkout in one step. If for whatever reason you do
several updates (or checkouts) of pieces of the tree, for the purpose
of obtaining a consistent snapshot of all of those pieces, then you
need to pass the rev number.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 23 21:09:50 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.