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

Re: 1.7.0 upgrade doesn't properly follow svn:externals

From: Scott Palmer <scott.palmer_at_digitalrapids.com>
Date: Fri, 9 Sep 2011 15:25:05 +0000

On 2011-09-09, at 11:14 AM, Neels J Hofmeyr wrote:

> On 09/09/2011 04:41 PM, Neels J Hofmeyr wrote:
>> And note that a .svn dir remains in XB/XC (seen in the final 'ls')
> I would like to add that 'upgrade' does leave the .svn folders behind
> everywhere, but running 'svn info' in the separate folders confirms that BX/
> is a 1.7 WC and BX/CX is not.
> ~Neels

I was actually wondering when you mentioned it if .svn folders weren't expected to be in "external" working copies. I'm just so used to how Subversion has worked in the past. I expect any sub-tree of my working copy to function as a working copy even if it was moved elsewhere. While it shouldn't be a problem to come around to the new way, I though that externals might somehow be an exception - as if they were an independent checkout.

Btw, I haven't had a chance to go back to 1.6 to test - is the issue with svn:externals referencing a file fixed? It used to add the file as both an external and a regular file so it was conflicting with itself.

Received on 2011-09-09 17:32:59 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.