git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Jonathan Leonard <johanatan@gmail.com>, git@vger.kernel.org
Cc: John Albietz <inthecloud247@gmail.com>
Subject: Re: .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent
Date: Thu, 29 May 2014 13:35:41 +0200	[thread overview]
Message-ID: <53871B8D.40608@web.de> (raw)
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?

  reply	other threads:[~2014-05-29 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29  2:07 .gitmodules containing SSH clone URLs should fall back to HTTPS when SSH key is not valid/existent Jonathan Leonard
2014-05-29 11:35 ` Jens Lehmann [this message]
2014-05-29 18:49   ` Junio C Hamano
2014-05-29 23:12   ` Jonathan Leonard
2014-05-29 23:56     ` Jeff King
2014-05-30  4:51     ` Chris Packham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53871B8D.40608@web.de \
    --to=jens.lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=inthecloud247@gmail.com \
    --cc=johanatan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).