That sounds great!
Just curious - where does this fall on the priority list of things to
do? Is it a 1.1 feature, or 2.0? (or it just depends on the amount of
work?)
Thanks,
Will
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Thursday, March 25, 2004 9:40 AM
> To: William Lentz
> Cc: dev@subversion.tigris.org
> Subject: Re: svn:externals feature(s)
>
>
> On Thu, 2004-03-25 at 11:35, William Lentz wrote:
>
> > Would anyone else find these features useful? Right now CVS can do
> > most of the above with modules but SVN and svn:externals is _much_
> > harder and less intuitive to use.
>
> Absolutely agreed. We've known about these shortcomings for a while,
> and have some abstract plans to fix them. The design isn't crystal
> clear yet: at the moment, we're thinking the "real" solution to the
> problem is to simply allow completely unrelated working copies (from
> unrelated repositories) to "link" to each other directly via entries
> files. Then svn:externals essentially becomes something only used by
> 'svn checkout' to assemble a composite working copy. After
> you have the
> working copy, all other commands just "work", and the svn:externals is
> ignored.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 25 18:50:57 2004