Re: .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent

Am 29.05.2014 04:07, schrieb Jonathan Leonard: The title pretty much says it all. But you do not give much information about your special use case. I assume you have submodule repositories for which some developers have a valid ssh key and others don't (maybe because they should only have read

Re: .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent

Jens Lehmann jens.lehm...@web.de writes: Am 29.05.2014 04:07, schrieb Jonathan Leonard: The title pretty much says it all. But you do not give much information about your special use case. Perhaps git grep insteadOf Documentation/ is all that is needed? -- To unsubscribe from this list:

Re: .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent

But you do not give much information about your special use case. I assume you have submodule repositories for which some developers have a valid ssh key and others don't (maybe because they should only have read access via https)? Precisely. Specifically this is for a collection (17 or

Re: .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent

On Thu, May 29, 2014 at 04:12:38PM -0700, Jonathan Leonard wrote: We are using GitHub. [...] But why is https special? Why not fall back to the git protocol? Or http? (And no: I'm not serious here ;-) HTTPS isn't special except in that it is the least privileged transport type (and

Re: .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent

On Fri, May 30, 2014 at 11:12 AM, Jonathan Leonard johana...@gmail.com wrote: But you do not give much information about your special use case. I assume you have submodule repositories for which some developers have a valid ssh key and others don't (maybe because they should only have read