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 [thread overview]
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.
next prev parent reply other threads:[~2018-01-10 16:14 UTC|newest]
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 ` How to use multiple SSH keys on Git exe (not bash) 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 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
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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).