git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How can I specify a non-standard TCP port for a git+ssh connection?

From
AJAndreas Jochens <aj@andaco.de>
Date
Dec 3, 2005, 21:43 UTC
Message-ID
<20051203214336.GA32003@andaco.de>
In-Reply-To
<7vwtimxait.fsf@assigned-by-dhcp.cox.net>
On 05-Dec-03 11:09, Junio C Hamano wrote:
> Having something on the command line to make it easy to override
> one-shot you might be able to talk me into, but not in a config
> file for git; there is a standard place to hold ssh
> configuration already.

You are right, a duplication of ssh config file options in git config files should not be necessary.

A way to specify a non-standard port for ssh on the command line would be sufficient. It is possible to specify non-standard ports for the git, http and rsync protocols on the command line. Why not for ssh?

Regards Andreas Jochens

Previous: Junio C Hamano
Message 4 of 4 in “Re: How can I specify a non-standard TCP port for a git+ssh connection?”
  1. linux@horizon.comDec 2, 2005
  2. Andreas JochensDec 3, 2005
  3. Junio C HamanoDec 3, 2005
  4. Andreas JochensDec 3, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.