I noticed that other proprietary SVN clients like SmartSVN just work out of the box handling such URLs:
svn+ssh://user@host:port/path I think this feature is very strategic to avoid abandoning TortoiseSVN. My working reality has shown it. My colleagues using Windows migrated from TortoiseSVN to SmartSVN when the company adopted a custom SVN port on our Phabricator. The company has no intention of changing ports and Windows users have no intention in handling weird configurations. As the result, proprietary software sadly win again. Il giorno lunedì 22 febbraio 2021 alle 09:06:48 UTC+1 Justin MASSIOT ha scritto: > Hello Roman, > > The standard way is to specify the port right inside the 'ssh' > definition of the SVN configuration (which is then used by 'svn+ssh'), > under the '[tunnel]' section. > I don't know if a port specified directly in the URL is supposed to work > or not, even in older versions.This may be more of an SVN concern than > something related to TortoiseSVN. Have you checked the SVN changelog? > > Justin > > Le jeudi 18 février 2021 à 16:28:41 UTC+1, Roman K a écrit : > >> >> I have running my ssh server on non-standard port and when I use >> svn+ssh:// >> me@myserver:port/path/to/repo i cannot connect unles I explicitly specify >> port to plink (under network settings) like >> >> "C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe" -P xxxx >> >> Previopus versions (up to 1.14.0) seemed to handle that properly fom url >> (:PORT part) so you could handle different repos on different servers with >> different ssh ports. But not now... >> > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/cd090375-3587-488b-ae73-81c7022b425dn%40googlegroups.com.
