This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Updated: cvs-1.11.17-1
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: cygwin at cygwin dot com
- Date: Mon, 20 Sep 2004 20:16:17 -0400
- Subject: Re: Updated: cvs-1.11.17-1
- References: <41490BB2.2030909@cwilson.fastmail.fm> <414EE963.50004@essic.umd.edu>
Joaquim Ballabrera wrote:
Dear Charles Wilson,
I'm a cygwin user and I have problems using CVS. I'm trying to use the
following command fron cygwin:
> cvs -d :ext:anoncvs@savannah.gnu.org:/cvsroot/gcc co -D 8/25/2004 gcc
The result is
' from cvs serverning: unrecognized response`ok
and then the program hangs.
The very same command works smoothly in a SGI workstation.
In both machines I have
setenv CVS_RSH ssh
I'm sorry, but I can't reproduce this. I've tried your exact command,
with 'export CVS_RSH=ssh' (I use bash, not a csh-ish shell). I've done
it in a working directory which is mounted in binary (unix) mode, and in
one which is mounted in text (DOS) mode. In both cases, it works
without error.
Now, that's started from a standstill (no previous checkout).
I note that when I do this 'beginning' checkout from a text mode working
directory, the following files have '^M' endings:
*/CVS/Entries
*/CVS/Entries.log
*/CVS/Repository
*/CVS/Root
*/CVS/Tag
That might be a bad thing -- since it would tend to mess up future
'update' checkouts (and cvs diffs, and ...) ***IF*** cvs is opening
those files for READ in binary mode (that is, not translating the '^M's
away).
But it doesn't.
I mean, cvs opens those files in the appropriate mode, stripping away
the '^M's as far as I can tell. I'm going to need more information.
"Run 'cygcheck -s -v -r > cygcheck.out' and include that file as an
attachment in your report. Please do not compress or otherwise encode
the output. Just attach it as a straight text file so that it can be
easily viewed."
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/