On Thu, Jan 29, 2015 at 11:15 PM, Stefan Sperling <s...@elego.de> wrote: > On Thu, Jan 29, 2015 at 11:01:32PM +0100, Stefan Kueng wrote: >> >On Thu, Jan 29, 2015 at 07:26:01PM +0100, Stefan Kueng wrote: ... >> >Well, I'd rather avoid having to make commits to multiple repositories. >> >If this feature only works for externals pointing at the same repository >> >then it's quite limited, isn't it? >> >> It's limited, but not as much as you might think. Such recursive externals >> are most often used in company internal setups, and there they all point to >> the same repository. So for all those, that's a big help and really >> required. > > How can we know that most people are using just one repository? > It's an assumption we can make, but we can't really know. > I think this is a severe limitation of the whole idea. And I'd rather not > encourage people to rely on externals within externals...
>From the peanut gallery: I'm with Stefan Küng on this. I think "intra-repository externals" are used *a lot*, especially in companies. I'm not a big fan of this way of working myself, but I can certainly see it happening (just a couple of months ago in my company someone reused an xml schema (which was relevant to three different subprojects) by using file externals). I think it's fine for some features to work only for intra-repos externals and not for, well, external externals :-). As long as it's clear to the user. (don't we have a similar limitation for e.g. 'svn commit --include-externals'?) -- Johan
