> Date: Mon, 25 Jan 2010 09:32:49 -0500 > Subject: Re: Externals within the same repository > From: andy.l...@gmail.com > To: gaff...@live.com > CC: users@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? Asbjørn _________________________________________________________________ Keep your friends updated—even when you’re not signed in. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010