You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Christopher Mann <ch...@infopol.fr> on 2004/09/10 18:38:08 UTC

Useing a non-standard ssh port in a svn+ssh://example.com:123456/repository

Hi,

It would be nice if the svn+ssh protocole use would incorporate the 
colon convention.
I mean :80 means port 80 and :123456 means port 123456.
That would be more handy then export SVN_SSH="ssh -p 123456" especially 
if I want to swith between different repositories.
It would be nice if other clients do this too.

Chris

-- 
Christopher Mann



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Useing a non-standard ssh port in a svn+ssh://example.com:123456/repository

Posted by Max Bowsher <ma...@ukf.net>.
Steve Greenland wrote:
> On Fri, Sep 10, 2004 at 10:45:20PM +0400, Mikhail Sobolev wrote:
> That said, it would be nice if the svn+ssh URLs followed the fairly
> standard :portnum convention.

Indeed it would - issue 1942 is an enhancement request for this.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Useing a non-standard ssh port in a svn+ssh://example.com:123456/repository

Posted by Steve Greenland <st...@lsli.com>.
On Fri, Sep 10, 2004 at 10:45:20PM +0400, Mikhail Sobolev wrote:
> On Fri, Sep 10, 2004 at 08:38:08PM +0200, Christopher Mann wrote:
> > It would be nice if the svn+ssh protocole use would incorporate the 
> > colon convention.
> > I mean :80 means port 80 and :123456 means port 123456.
> > That would be more handy then export SVN_SSH="ssh -p 123456" especially 
> > if I want to swith between different repositories.
> > It would be nice if other clients do this too.
> This is implemented using different approach.  See
> 
>     http://svnbook.red-bean.com/svnbook/ch06s03.html#svn-ch-6-sect-3.3

Another way is to use the .ssh/config file. Create entries like

host svn1
    Hostname svn.example.com
    Port 80
    ForwardAgent no
    ForwardX11 no

host svn2
    Hostname svn.example.com
    Port 123456
    ForwardAgent no
    ForwardX11 no

And then use svn1 or svn2 for the hostname in the subversion command
line. It's functionally the same as the alternate tunnel technique, but
I find it easier to remember this, and easier to type. YMMV.

That said, it would be nice if the svn+ssh URLs followed the fairly
standard :portnum convention.

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Useing a non-standard ssh port in a svn+ssh://example.com:123456/repository

Posted by Mikhail Sobolev <ms...@mawhrin.net>.
On Fri, Sep 10, 2004 at 08:38:08PM +0200, Christopher Mann wrote:
> It would be nice if the svn+ssh protocole use would incorporate the 
> colon convention.
> I mean :80 means port 80 and :123456 means port 123456.
> That would be more handy then export SVN_SSH="ssh -p 123456" especially 
> if I want to swith between different repositories.
> It would be nice if other clients do this too.
This is implemented using different approach.  See

    http://svnbook.red-bean.com/svnbook/ch06s03.html#svn-ch-6-sect-3.3

--
Misha