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

Re: SVN update of child ignores files if preceded by update --depth immediates

From: Mihai Danila <viridium_at_gmail.com>
Date: Thu, 5 Sep 2013 14:44:38 -0400

Just to make sure, is this supposed to be doable in parallel in SVN 1.7,
because it doesn't seem to be doable?

wc/objects/object1/ (1-2 dozen files)
wc/objects/object2/ (1-2 dozen files)
...
wc/objects/objectN/ (1-2 dozen files)

svn up wc/objects/object<i1>
svn up wc/objects/object<i2>
...
svn up wc/objects/object<ik>

(for a subset of the objects in that directory)

On Thu, Sep 5, 2013 at 2:14 PM, Philip Martin <philip.martin_at_wandisco.com>wrote:

> Mihai Danila <viridium_at_gmail.com> writes:
>
> > That's exactly the problem. In SVN 1.6 I was able to run concurrent SVN
> > updates on different directories. Their separate databases were
> updateable
> > separately. In 1.7, this is no longer possible.
>
> Both 1.7 and 1.8 allow concurrent updates but the update targets have to
> be a bit further apart than 1.6. Given a working copy layout:
>
> wc/
> wc/A/
> wc/A/B/
> wc/X/
> wc/X/Y/
>
> With 1.6
>
> svn up wc/A/B
>
> locks the whole tree for the explict target wc/A/B plus a lock on the
> parent directory wc/A, while 1.8 locks the whole tree for the parent
> wc/A. The result is that both 1.6 and 1.8 allow
>
> svn up wc/A/B
> svn up wc/X/Y
>
> in parallel, but only 1.6 allows
>
> svn up wc/A
> svn up wc/X/Y
>
> in parallel, and neither allows
>
> svn up wc/A
> svn up wc/X
>
> in parallel.
>
> --
> Philip Martin | Subversion Committer
> WANdisco // *Non-Stop Data*
>
Received on 2013-09-05 20:45:11 CEST

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