You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stuart Celarier <SC...@corillian.com> on 2005/10/17 16:53:25 UTC
Checkout and update atomicity
When performing a checkout or update from the HEAD, is there a guarantee
that all items belong to a single revision? That would mean "checkout
(update) from the HEAD" means "checkout (update) the revision that was
the latest at the time the operation began." Is that how Subversion
behaves?
Cheers,
Stuart
Stuart Celarier | Corillian Corporation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Checkout and update atomicity
Posted by Scott Palmer <sc...@2connected.org>.
On 17-Oct-05, at 1:21 PM, Ryan Schmidt wrote:
>
> On Oct 17, 2005, at 18:53, Stuart Celarier wrote:
>
>
>> When performing a checkout or update from the HEAD, is there a
>> guarantee
>> that all items belong to a single revision? That would mean "checkout
>> (update) from the HEAD" means "checkout (update) the revision that
>> was
>> the latest at the time the operation began." Is that how Subversion
>> behaves?
Yes. But if you use svn:externals be aware that fetching the
external is counted as a separate operation, and so if the external
points to the same repository it may get a later revision of that
repository.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Checkout and update atomicity
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Oct 17, 2005, at 18:53, Stuart Celarier wrote:
> When performing a checkout or update from the HEAD, is there a
> guarantee
> that all items belong to a single revision? That would mean "checkout
> (update) from the HEAD" means "checkout (update) the revision that was
> the latest at the time the operation began." Is that how Subversion
> behaves?
I'm pretty sure that's a "Yes." Over HTTP, for example, all the data
comes in a single response from Apache.
An update is not necessarily atomic though: it's possible for an
update to encounter a problem with your working copy halfway through,
in which case only have of it will be updated, and the rest won't.
You can fix whatever the problem was and issue another update.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org