Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Date: Fri, 4 Feb 2011 02:37:11 +0200
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bob Archer <Bob.Archer@amsi.com>
Cc: Ryno Changuion <ryno.changuion@za.thalesgroup.com>,
	"users@subversion.apache.org" <users@subversion.apache.org>
Subject: Re: Copy with externals, then commit fails
Message-ID: <20110204003711.GL25076@daniel3.local>
References: 
 <344D1ECFB7D9904EA70F9AF171638B5304D5DE9C@midexchange.Adsintranet.Corp>
 <CB4587DA62024B40B9F929ECF639210F2C7687D86E@USALWEXMB4.infor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CB4587DA62024B40B9F929ECF639210F2C7687D86E@USALWEXMB4.infor.com>
User-Agent: Mutt/1.5.18 (2008-05-17)

Bob Archer wrote on Tue, Feb 01, 2011 at 13:32:18 -0500:
> File externals require that the file being pointed to is in the same
> working copy as the external of it. From the docs:
> 
> "While directory externals can place the external directory at any
> depth, and any missing intermediate directories will be created, file
> externals must be placed into a working copy that is already checked
> out."
> 

This quoted part talks about where the pointer will be created, not
about where the pointed-to file should live.  (Currently the only
restriction on that is that it should be in the same repository as the
svn:externals property.)

> BOb
>