On Tuesday, April 22, 2008 2:18 PM Karl Fogel wrote:
>Blair Zajac <blair_at_orcaware.com> writes:
>> Here's my current thinking on behavior and implementation.
>>
>> - Support only intra-repository file externals. This will allow the
>> svn client to effectively do a 'touch foo; svn add foo; svn switch
URL
>> foo' to have a external in the wc (those actual commands only work in
>> a 1.5 client). So unlike a directory external, the .svn/entries file
>> has entries for file externals. This is needed for supporting all
the
>> client commands on a file. I don't see modifying the existing
>> directory behavior.
>
> Before implementing this, it might be good to find out how often
people
> use intra-repository externals at all. My guess (uneducated,
anecdotal,
> etc) is: not much. Certainly most of the externals I set are coming
> from other repositories...
I believe that this depends upon your repository project layout. Those
who utilize the multiple projects in a single repository layout will
tend
to have intra-repository externals. Others who utilize the single
project
in multiple repositories layout will tend to have inter-repository
externals.
Overall, most of us probably have a mixed layout.
-Geoff
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-23 15:19:25 CEST