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
On Wed, Mar 3, 2010 at 05:14, Giulio Troccoli
giulio.trocc...@uk.linedata.com 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
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
giulio.trocc...@uk.linedata.com wrote:
Hello,
We are starting using externals to publish some
documentation for our customer
-
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
On Wed, Mar 3, 2010 at 05:14, Giulio Troccoli
giulio.trocc...@uk.linedata.com wrote:
Hello
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 says:
