Hi, On Fri, 25 May 2007, Sven Verdoolaege wrote: > On Fri, May 25, 2007 at 09:16:30AM -0700, Junio C Hamano wrote: > > Sven Verdoolaege <skimo@xxxxxxxxxx> writes: > > > So, I think it would still be useful to have an optional additional > > > out-of-tree mechanism of getting usable URLs if the URLs in .gitmodules > > > or your local config don't work. > > > > I thought that was already solved in my original two-level > > strawman and can naturally be extended to the three-level > > strawman. What am I missing? > > Maybe I'm missing something but you only seem to talk about .gitmodules > and local config there, while this would be a way of automatically getting > URLs that are either not available in .gitmodules or the local config > or are outdated or should be overridden. I do not see what you're getting at. Either you want to fetch the URLs from an upstream, in which case they should be fetched. Why not in ".gitmodules"? If the URLs don't work, you should blame the maintainer, not fsck up the tool. Or you want some sort of "fallback" set of URLs. I cannot think of any reasonable use case here. Or you want to receive overrides, such as when a submodule has moved, so that it still works when you check out older versions (and do not have the objects locally already). But to make such overrides automatic wreaks havoc IMHO. Also, this is rare enough that I'd rather not fsck up an elegant solution, where you have to treat such special cases manually, for something which affects "normal" users, which just track the project. Maybe I'm wrong. But then, Josef is right, we can talk about that later. It's not like you need a feature like that from day one. Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
