On Fri, Jun 29, 2007 at 02:54:36PM +0100, Tom Evans wrote:
> Did you miss Albert Shih's reply (slightly modified)?
Actually, I was reading replies from the top of the thread down, and was
still looking into what he said (in the midst of dealing with other
things that came up), so hadn't gotten back to the list yet.
> > Put something like
> > [tunnels]
> > myssh=/usr/bin/ssh -p 1234 123.45.678.90
> > in
> > ~/.subversion/config
> > and use
> > svn co svn+myssh://usr/home/svn-repos/project
> You can then clearly define as many transports as you like, which
> requires no setting of environment variables and is shell-agnostic.
> Full details are described in the redbook:
> In fact, if you had read the svn+ssh portion of the redbook, you would
> have come across this sentence:
> "This example demonstrates a couple of things. First, it shows how to
> make the Subversion client launch a very specific tunneling binary (the
> one located at /opt/alternate/ssh) with specific options. In this case,
> accessing a svn+joessh:// URL would invoke the particular SSH binary
> with -p 29934 as arguments ??? useful if you want the tunnel program to
> connect to a non-standard port."
> Reading the manual is good.
Apparently, reading it *recently* -- rather than just skimming to refresh
my memory -- seems to be key in this case.
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
print substr("Just another Perl hacker", 0, -2);
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"