hi Glenn,

> Could it be a problem with your version ssh.exe?  Or, have you
> ssh'ed into the sourceforge server at least once?

My CVS access worked fine once upon a time, when the DQSD sourceforge CVS
repository was first created.  I don't know if I've changed ssh versions, but
I don't have any problems ssh'ing anywhere else; I'm fairly certain I'm
running the most recent version...  My SSH client was installed with cygwin,
and I can successfully ssh to cvs.dqsd.sourceforge.net (of course, the server
boots you jsut after you log in, but the fact that I can connect proves that
the client works.)


> I use TortoiseCVS [1] which doesn't use ssh, but something it
> supplies called plink for secure transfers.  You might give
> that a try to see if it at least works.
>
> [1] http://www.tortoisecvs.org/


hheheh, I'm familiar with TortoiseCVS, I remember suggesting it to someone
when I wrote up a simple CVS tutorial/howto for them.

(iirc correctly, you said that you preferred WinCVS over TortoiseCVS at the
time!)

Anyway, I'll poke around and see if I can't get things fixed.


Nik



-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to