From: Junio C Hamano <junkio@cox.net>
To: Martin Sivak <mars@nomi.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] GIT_SSH alternate ssh name or helper
Date: Wed, 03 Aug 2005 10:12:53 -0700 [thread overview]
Message-ID: <7viryndjvu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20050803151542.GA6655@medusa
Martin Sivak <mars@nomi.cz> writes:
> This patch make possible to use alternate ssh binary or ssh helper
> script. The script can be used to give additional parameters to ssh
> binary (like private key, protocol version, ...).
>
> Example script could look like this:
>
> #!/bin/sh
> ssh -1 -i myprivatekey.key "$@"
>
> The patch itself is realy very simple:
I understand why you would want this if your ssh binary is
called something other than ssh [*1*], but I doubt the example
you gave needs this patch. Could you explain why having
something like this in your .ssh/config file is not enough?
Host foo.bar.xz
Protocol 1
IdentityFile ~/.ssh/privatekey.key
Even if you wish to use different settings between git and
interactive, I presume you could do something like this:
# for interactive
Host foo.bar.xz
Protocol 2
# real repo is foo.bar.xz:/pub/scm/git/git.git/ but pull with
# git-foo.bar.xz:/pub/scm/git/git.git/
Host git-foo.bar.xz
Hostname foo.bar.xz
Protocol 1
IdentityFile ~/.ssh/privatekey.key
[Footnote]
*1* and even in that case you can trivially fix it by having
a small wrapper in $HOME/bin/ssh:
#!/bin/sh
exec ssh-installed-under-nonstandard-name "$@"
next prev parent reply other threads:[~2005-08-03 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 15:15 [PATCH] GIT_SSH alternate ssh name or helper Martin Sivak
2005-08-03 17:12 ` Junio C Hamano [this message]
2005-08-03 18:56 ` Martin Sivak
2005-08-03 19:29 ` Junio C Hamano
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=7viryndjvu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mars@nomi.cz \
/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).