All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Vilz 'niv' <niv@iaglans.de>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>, git@vger.kernel.org
Subject: Re: how to pass ssh options to git?
Date: Thu, 02 Nov 2006 12:18:48 +0100	[thread overview]
Message-ID: <4549D418.3050606@iaglans.de> (raw)
In-Reply-To: <20061102093153.GF7468@mellanox.co.il>

Michael S. Tsirkin wrote:
> Quoting r. Matthieu Moy <Matthieu.Moy@imag.fr>:
>> Subject: Re: how to pass ssh options to git?
>>
>> "Michael S. Tsirkin" <mst@mellanox.co.il> writes:
>>
>>> How is it possible to pass ssh options to git?
>>> for example, I use these options to log into some machine:
>>> ssh -i <private> -o HostKeyAlias=<alias> -p <port> -l <user> <address>
>> Not answering the question, but this can go to ~/.ssh/config :
>>
>> Host *.domain.net
>> User some_user
>> IdentityFile ~/.ssh/foobar
>>
> 
> I know, problem is I want to use different options at different times.
> I could use -F configfile ssh option, but how to pass *that* to git?

you can setup different host-entries as kind of virtual hosts in your 
hosts-section. that is what i do

host blah1.domain.net
hostname www.domain.net
user blah1
IdentityFile .ssh/blah
Port 523434

host blah2.domain.net
hostname www.domain.net
user blah1
IdentityFile .ssh/blah
Port 22

The first host-section i use in an environment, where i cannot get 
through port 22.


Sincerly

      parent reply	other threads:[~2006-11-02 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02  9:07 how to pass ssh options to git? Michael S. Tsirkin
2006-11-02  9:20 ` Matthieu Moy
2006-11-02  9:31   ` Michael S. Tsirkin
2006-11-02 11:06     ` Dennis Stosberg
2006-11-02 11:27       ` Michael S. Tsirkin
2006-11-02 16:10         ` Linus Torvalds
2006-11-02 20:22           ` Shawn Pearce
2006-11-02 11:18     ` Nicolas Vilz 'niv' [this message]

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=4549D418.3050606@iaglans.de \
    --to=niv@iaglans.de \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.