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
Junio C Hamano <junkio@cox.net>
Date
Dec 3, 2005, 19:09 UTC
Message-ID
<7vwtimxait.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051203080620.GA22032@andaco.de>
Andreas Jochens <aj@andaco.de> writes:
> This is a nice feature, of course. But I still have to edit a separate 
> config file. In some cases (e.g. scripts using ad hoc port forwarding) it 
> would be much easier if the non-standard port and maybe some other
> options could be specified directly on the git command line or

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.

Previous: Andreas JochensNext: Andreas Jochens
Message 3 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.