git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jens Lehmann <jens.lehmann@web.de>
Date
May 29, 2014, 11:35 UTC
Message-ID
<53871B8D.40608@web.de>
In-Reply-To
<CA+OJ3uv0XqeodTCzeauUrH9FjzknBupMd5kxh+3qgyji5TwOzA@mail.gmail.com>
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 access via https)?

If that is the case you might want to look into access control tools like gitolite.

>  Lack of this feature (or presence
> of this bug [depending on your perspective]) is a major PITA.

But why is https special? Why not fall back to the git protocol? Or http? (And no: I'm not serious here ;-)

After the first failed clone of the submodule at via SSH the developer could also just do a

   git config submodule.<name>.url https://host/repo
and override the URL from .gitmodules.
But maybe I misunderstood why you want to have a fall back?
Previous: Jonathan LeonardNext: Junio C Hamano
Message 2 of 6 in “.gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent”
  1. Jonathan LeonardMay 29, 2014
  2. Jens LehmannMay 29, 2014
  3. Junio C HamanoMay 29, 2014
  4. Jonathan LeonardMay 29, 2014
  5. Jeff KingMay 29, 2014
  6. Chris PackhamMay 30, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.