> In that case you would need the "URL mappings", perhaps as a per-remote > attribute. That is, you could configure: > > "When I am doing git pull fred, do git submodule update but > apply remote.fred.subrewrite sed script on each URL before > fetching the submodule." > > Still, that feels quite hackish to me, and I'm not convinced that your > workflow cannot be adjusted so that users merge only the next-to-last > commit of a branch instead of the last one. > Hm - I'm still disliking having 'special' commits to change .gitmodules. I can hack scripts to make it work, but it would be nice to have a UI that is generally useful. Thinking out loud, could we have in .git/config something like [submodule "moduleA"] url = git://origin.com/path/to/.git # Current place of origin fred.url = git://fredcomputer/path/to/freds/moduleA.git # where fred declares moduleA to come from local = git://myhost/working/copy/super/moduleA/.git # where other people can get access to *my* moduleA repo So if I look in the git repository of fred (as specified in my [remote "fred"], I can see their "local" entry, and enter that as fred.url in my config And the ability to do (e.g) $ git submodule init fred $ git submodule update fred ? -- 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
