On Fri, Jul 18, 2008 at 10:16 AM, Petr Baudis <pasky@xxxxxxx> wrote: > snip > > "How do we mass-supply custom submodule URLs when publishing the > customized main repository at a custom location too?" > Yes - that is an additional problem. If I may expand the usecase just so it's clear (and to check we're talkiing the same language) I do something like $ git remote add fred git://fredcomputer/superproject/.git $ git fetch --submodules fred And when the recursive fetching enters a submodule, it is trying itself to do something like $ git fetch fred At which point 1) the submodule also has a remote specified for fred. In which case it can continue 2) the submodule doesn't have remote specified for fred. How to solve this case? (I.E how does 'my' git 'discover' where fred's git repositories are for the submodules?) a) By getting some information from fred, either in *Fred's* superproject .git/config (or some other readable file) b) By reading some information out of the superproject .gitmodules that has been fetched from fred c) By calculating a relative URL based on the supposition that fred has working copies laid out in the filesystem. I was tentatively suggesing (c), with a backup of (a) for the minority cases where you weren't pulling from a person but from a mirror or something. Having the client edit config files just feels like a hack to me, regardless of whether scripts are enabled to do it. -- 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
