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

Re: Svn17: concurrent commits in differnt parts of your WC

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 19 Apr 2012 15:24:12 +0100

Derek Wallace <Derek.Wallace_at_intunenetworks.com> writes:

> 1. This comment
> in parallel but at the cost of not allowing
> cd A/B/X ; svn up
> to delete A/B/X. <---- whats this?

When you run "cd A/B/X ; svn up" X will get updated to HEAD. If X is no
longer present in HEAD because it has been deleted then the update could
attempt to remove A/B/X from the working copy just like any other
deleted directory. 1.6 doesn't attempt the delete partly because A/B is
not locked.

> 2. why does this work in svn 1.7.

It also works in 1.6.

> Will they both not put a lock in the .svn folder beside A.
>
> svn up A/X/Y
> svn up A/P/Q

When you run "svn up A/X/Y" Y gets locked because it is going to change,
and X gets locked because it was required in 1.6 since deleting Y would
modify X/.svn/entries. 'A' doesn't change so doesn't get locked.

[Although 1.7 currently locks X it's possible that this is simply
inherited from 1.6 and it may be possible to change it in the future.]

-- 
Philip
Received on 2012-04-19 16:24:52 CEST

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