[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Blanks in PuTTY session names

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-07-27 17:14:08 CEST

Christoph Zwerschke wrote:

> I recapitulate my problem with blanks in PuTTY session names:
>
> In the "settings" dialog, I have set TortoisePlink.exe as ssh client.
>
> In version 1.1.7 (build 3240) it was possible to access remote
> repositories with a URL like that:
> "svn+ssh://my putty session/svnroot/repos/project".
> Here, "my putty session" is a session saved in PuTTY with that name.
>
> However, since version 1.2.0 (build 3602) this does not work anymore.
> It seems that TSVN is not looking for the PuTTY session with the name
> "my putty session", but for a PuTTY session with the name
> "my%20putty%20session" which does not exist.
>
> If I am allowed to make another uneducated guess, could this be a result
> from the changes in revision 3323 in SVN.cpp and TSVN.cpp?

Christoph,

I sure can understand your frustration about this. But you should see
that if all direct URLs work (i.e. not URLs to PuTTY session names but
URLs to actual repositories) then it can't be a bug in TSVN.
Maybe its a bug in the Subversion API (where they pass the URL to the
SSH client). To find that out, try the Subversion CL client with such
URLs to PuTTY sessions. If there too it works for 1.1.x clients but
fails for 1.2.x clients, you should report it to the Subversion guys.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Jul 27 17:16:27 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.