Mihai Danila 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
b
Understood, thank you for this clarification.
On Thu, Sep 5, 2013 at 2:56 PM, Philip Martin wrote:
> Mihai Danila writes:
>
> > 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
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
svn up wc/objects/object
...
svn up wc/obje
Mihai Danila writes:
> 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
> sv
f child ignores files if preceded by update --depth
immediates
Philip,
We have upgraded our working copies to SVN 1.7, but, unfortunately, the single
".svn" directory per working copy paradigm used by SVN 1.7 prevents us from
running concurrent updates to different areas of our wor
ember 04, 2013 3:13 PM
> *To:* Philip Martin
> *Cc:* dev@subversion.apache.org
> *Subject:* Re: SVN update of child ignores files if preceded by update
> --depth immediates
>
> ** **
>
> Philip,
>
> ** **
>
> We have upgraded our working copies to SVN 1.7,
On 9/5/13 10:05 AM, Mihai Danila wrote:
> Can we simply fix the original issue in SVN 1.6 instead?
1.6 is no longer being supported as of the 1.8.x release.
https://subversion.apache.org/docs/release-notes/1.8.html#svn-1.6-deprecation
Philip,
We have upgraded our working copies to SVN 1.7, but, unfortunately, the
single ".svn" directory per working copy paradigm used by SVN 1.7 prevents
us from running concurrent updates to different areas of our working copy.
We get errors and locked working copies.
Is it possible to fix SVN
Thank you Philip. We will upgrade to a newer SVN version.
On Thu, Aug 8, 2013 at 1:34 PM, Philip Martin wrote:
> Mihai Danila writes:
>
> > With Subversion 1.6.5, 1.6.13, and I believe Subversion 1.7 also, I
> noticed
> > the following bug, which I first asked about on StackOverflow about and
>
Mihai Danila writes:
> With Subversion 1.6.5, 1.6.13, and I believe Subversion 1.7 also, I noticed
> the following bug, which I first asked about on StackOverflow about and had
> independently confirmed (
> http://stackoverflow.com/questions/18114102/strange-svn-behavior-missing-files-when-using-
10 matches
Mail list logo
