Michael Tiller wrote:
> I've got an idea. Please feel free to tell my why it is a bad idea (I
> looked in the issue tracker and I didn't see anything that looked like
> this).
>
> The svn:externals functionality is extremely useful (at least for me).
> But it is such a pain to use. It seems to me that a very intuitive way
> to add the functionality would be to allow a "SVN Checkout..." inside a
> working copy. That is effectively what an svn:externals is right? The
> point being that if you do an SVN Checkout within a working copy that
> implicitly means an svn:externals. The dialog would be exactly the same
> right? But instead of doing a real "checkout" you'd be adding the
> svn:externals property. If it already existed, you'd be appending to
> it. If you removed the directory you'd be removing it, etc.
>
> Doesn't this seem like an intuitive way to support svn:externals and
> simultaneously reuse much of the infrastructure (e.g. dialogs) already
> in TortoiseSVN?
>
> OK...now tell me why it's a bad idea. I'm assuming it is because
> otherwise it would already be implemented like all the other extremely
> cool (and very user friendly) features in TSVN.
Because you can check out another working copy without using externals.
That's then called a "nested layout", and even though it's not a good
idea to do that, people make use of that.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Feb 13 19:27:25 2007