On 29 October 2013 04:36, Dave Abrahams
The super-project can't use github's git urls as they don't allow anonymous access. I believe the super-project should be using https for submodules, rather than http.
Why is that? Because it's possible to commit through https?
Yes.
But won't someone complain that they can't access https behind their corporate firewall? It always seems like there's no right answer in this territory.
Oh right, I hadn't thought of that. Making it easy to check out probably should be the priority.
Passwords for https can be stored using password caching:
https://help.github.com/articles/set-up-git#password-caching
But if you'd rather use git urls in order to use your ssh key, you can use git's 'insteadOf' configuration option.
Oh, nifty; I didn't know about this!
http://stackoverflow.com/questions/1722807/git-convert-git-urls-to-http-urls https://coderwall.com/p/sitezg
Given the propensity of various access methods to fail for various reasons, I think we probably ought to suggest the use of insteadOf right in the instructions, no matter how we decide to write the URIs.
OK. Going back to Beman's question, I haven't tested it yet, but I think the configuration command is: git config --global url."git@github.com:boostorg/".insteadOf "http://github.com/boostorg/" This just updates the .gitconfig file, so it can be edited later if it doesn't work.