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

RE: Externals within the same repository

From: Asbjørn Sæbø <gaffe_1_at_live.com>
Date: Mon, 25 Jan 2010 15:54:32 +0100

> Date: Mon, 25 Jan 2010 09:32:49 -0500
> Subject: Re: Externals within the same repository
> From: andy.levy_at_gmail.com
> To: gaffe_1_at_live.com
> CC: users_at_subversion.apache.org
> On Mon, Jan 25, 2010 at 09:14, Asbjørn Sæbø wrote:
>> Assume the following situation: There is a repository my_repo, structured like this:
>> my_repo
>> my_repo/trunk
>> my_repo/trunk/a
>> my_repo/trunk/a/file.h
>> my_repo/trunk/b
>> where my_repo/trunk/b has an svn:external to import the contents of my_repo/a.
>> That is, b will have the contents of a external-ed in.
>> Is this valid and sound SVN?
> Yes, just be careful to avoid any recursive externals - having an
> external in a pointing at b, while having an external in b pointing at
> a, would probably result in your WC filling all available disk space.
> Last I knew, Subversion did not check for recursion in externals.

OK.  But it does seem a bit weird, though.  When doing a fresh check out
of this, all these "internal externals" do show up as "merged" in the
check out log.

As TortoiseSVN presents it:
External C:\asa\my_repotrunk\a\file.h
Merged C:\asa\my_repotrunk\a\file.h

Since this was a clean check out, there should not really be any merging
going on, so this message seems a bit confusing.
Any comments?


Keep your friends updated—even when you’re not signed in.
Received on 2010-01-25 15:55:10 CET

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

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