Peter Kennard <peterk@livingwork.com> wrote on 11/06/2006 12:47:52 PM:
> >Instead of using the cygwin ssh, use the Tortoise plink.exe
"windowless" ssh
> >client in your ~/.subversion/config file. I do not think you can use
the
> >same keys as ssh, though there may be a conversion mechanism.
>
> Actually this is with the Tortoise "Explorer" plugin when it uses the
> cygwin or other third party ssh programs. I assume because it is
> using the same C library.
>
> Pardon my ranting - finally after many years eclipse got so I could
> have ssh2/cygwin support in the eclipse CVS module, and now I am
> having to revisit the exact same set of problems now that subversion
> is happening :) Subversion in general is a fabtastic improvement on CVS.
>
> I am now being asked by my empoyer to convert to subversion (I have
> wanted to for a while) I will try to get them to donate some $$ to
> eclipse and subversion projects. I myself donate to debian every
> time I install it :).
>
> At least now things are starting to work with the ssl/apache server,
> though the cygwin subversion client has some bugs with the
> .svn/entries file permissions handling on windows. Now I have to
> generate ssl client keys for all the developers ...
Client certs are another area where JavaSVN works better than the native
libraries.
Did you get the svn command like working witj your Cygwin SSH client? If
you did, and you start Eclipse from a command shell, then your SSH prompts
should appear and be answerable from within the shell.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Nov 6 18:59:33 2006