Maybe this is obvious, but my brief search with Google turned up nothing.
Perhaps it's so obvious that people don't bother noting, but in case there
is someone else who's as dull as me, here's a workaround I found.
To tunnel svn over SSH using a non-standard SSH port, you create a PuTTY
saved session with the desired port, since TortoiseSVN supports
"svn+ssh://username@SavedSession/path" syntax, but not
"svn+ssh://username@hostname:port/path" syntax. This is fine if you only
use TortoiseSVN. However, it's problematic when you also use a different
svn client, one that does support the second syntax (such as Subversive).
This is because the URL is stored verbatim with the working copy.
It turned out that PuTTY allows saved sessions with names containing colon
and period, and TortoiseSVN checks for saved sessions before resolving host
names. Therefore, the solution is to name the saved session
"hostname:port".
For example, suppose the URL is "svn+ssh://devel@example.com:2222/Program".
Then, create a saved session named "example.com:2222". This way, both
TortoiseSVN and Subversive can access the same working copy without hiccups.
Julian Hsiao
madoka@nyanisore.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Jan 31 18:41:49 2007