> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible about what
> you were trying to do.
> But please first search t
On Jul 23, 2010, at 12:33 PM, Daniel Shahaf wrote:
> Is anything printed to stderr?
Yes, it says that the connection was forceably closed by the server. I think
our svn server is running out of memory sometimes.
>
> Harvey Chapman wrote on Fri, Jul 23, 2010 at 12:06:03 -0400:
>>C:\>svn --v
Is anything printed to stderr?
Harvey Chapman wrote on Fri, Jul 23, 2010 at 12:06:03 -0400:
> C:\>svn --version
> svn, version 1.6.6 (r40053)
>compiled Oct 26 2009, 20:14:36
> Copyright (C) 2000-2009 CollabNet.
>
> I have a small repository with some large externals. When the
C:\>svn --version
svn, version 1.6.6 (r40053)
compiled Oct 26 2009, 20:14:36
Copyright (C) 2000-2009 CollabNet.
I have a small repository with some large externals. When the externals fail to
update or checkout completely, the action continues with the next external or
the mai
> The problem is that you're using file externals combined with
> putting the external locally in a directory which is not
> already a working copy. That's not supported for file externals.
>
> See
> http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html.
> Somewhere near the end it say
ssage-
>
>
>> From: Andy Levy [mailto:andy.l...@gmail.com]
>> Sent: 03 March 2010 11:31
>> To: Giulio Troccoli
>> Cc: users@subversion.apache.org
>> Subject: Re: Update failed with "is not a working copy"
>> message on externals
>>
>&g
; To: Giulio Troccoli
> Cc: users@subversion.apache.org
> Subject: Re: Update failed with "is not a working copy"
> message on externals
>
> On Wed, Mar 3, 2010 at 05:14, Giulio Troccoli
> wrote:
> > Hello,
> >
> > We are starting using externals to pub
On Wed, Mar 3, 2010 at 05:14, Giulio Troccoli
wrote:
> Hello,
>
> We are starting using externals to publish some documentation for our
> customer. The repository contains test files and documentation about the
> testing. Some of these files and docs need to be made available to our
> customer.
Hello,
We are starting using externals to publish some documentation for our customer.
The repository contains test files and documentation about the testing. Some of
these files and docs need to be made available to our customer. So I thought of
creating a Public folder and define the svn:exte
