git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Sam Millman'" <sam.millman@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: How to use multiple SSH keys on Git exe (not bash)
Date: Wed, 10 Jan 2018 11:14:11 -0500
Message-ID: <000d01d38a2e$10559810$3100c830$@nexbridge.com> (raw)
In-Reply-To: <CALKyTE4eqbw_kMEH9fpwFa-s-WagFn5j9OxK68YXoARm7f4zHQ@mail.gmail.com>

On January 10, 2018 11:01 AM Sam Millman wrote:
> That would mean I would need to change the case for a letter everytime I
> have a repo with a new key, that would mean I would be restricted to
> 12 client repos at a time :\, seems very hacky to me
> 
> On 10 January 2018 at 15:58, Randall S. Becker <rsbecker@nexbridge.com>
> wrote:
> > The ~/.ssh/config file is case sensitive by definition when it comes to Host
> and HostName. Try bitbucket.org for one and Bitbucket.org for another. You
> will have to change the remote URL accordingly to pick up the correct
> identity.

The combinatorics of it is Sum i=1 to n.(i) = 78.

You can also use BUtbucket.org, bUTbucket.org, etc., BUTbucket.org, etc., etc.

Hacky, maybe, but it has worked that way for a long time. Why do you need more than 78 identities? Bitbucket allows you to be on multiple projects with the same identity.


  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALKyTE7+qJSYHQRB44HjHXK_EjOxNnCfQOROSDVVwAFR-gMnXQ@mail.gmail.com>
2018-01-10 15:30 ` Sam Millman
2018-01-10 15:58   ` Randall S. Becker
2018-01-10 16:01     ` Sam Millman
2018-01-10 16:14       ` Randall S. Becker [this message]
2018-01-10 15:58   ` Ævar Arnfjörð Bjarmason
2018-01-10 16:02     ` Sam Millman
2018-01-10 16:23       ` Randall S. Becker
2018-01-10 16:26         ` Sam Millman
2018-01-10 16:29           ` Randall S. Becker
2018-01-10 16:32             ` Sam Millman

Reply instructions:

You may reply publically 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='000d01d38a2e$10559810$3100c830$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=sam.millman@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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox