Re: core.sshCommand and url.*.insteadOf for submodules

2017-01-05 Thread Stefan Beller
On Thu, Jan 5, 2017 at 9:02 AM, Jeff King wrote: > On Thu, Jan 05, 2017 at 05:53:30AM -0800, Stefan Beller wrote: > >> > My scenario is as follows: I use 2 SSH keys for GitHub, for private and >> > work-related repositories. My default key is my private key. So when I >> > clone a work repository

Re: core.sshCommand and url.*.insteadOf for submodules

2017-01-05 Thread Jeff King
On Thu, Jan 05, 2017 at 05:53:30AM -0800, Stefan Beller wrote: > > My scenario is as follows: I use 2 SSH keys for GitHub, for private and > > work-related repositories. My default key is my private key. So when I > > clone a work repository and try getting the submodules, `git submodule > > updat

Re: core.sshCommand and url.*.insteadOf for submodules

2017-01-05 Thread Stefan Beller
On Thu, Jan 5, 2017 at 2:09 AM, Stefan Schindler wrote: > Hello mailing list, > > it seems like that the `core.sshCommand` and `url.*.insteadOf` > configuration settings do not apply to `git submodule update --init` > (and probably related) calls. > > Is this intentional? The original design of s

core.sshCommand and url.*.insteadOf for submodules

2017-01-05 Thread Stefan Schindler
Hello mailing list, it seems like that the `core.sshCommand` and `url.*.insteadOf` configuration settings do not apply to `git submodule update --init` (and probably related) calls. Is this intentional? My scenario is as follows: I use 2 SSH keys for GitHub, for private and work-related reposito