X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <ddc185be0809290651q5430742csb1d09f002ff0a24e@mail.gmail.com>
Date: Mon, 29 Sep 2008 17:51:00 +0400
From: "Dmitry Semyonov" <linulin AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: cvs client is too verbose since update to 1.11.22.1 (or earlier?) version
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

It looks like some debugging logs were accidentally switched on in cvs
client sources. They appear even if -q option is used. Note that
everything works as expected except for these annoying log messages at
the end:

cvs update: closing down connection to cvs.example.com

cvs commit: closing down connection to cvs.example.com: No such file
or directory

cvs checkout: closing down connection to cvs.example.com: No such file
or directory

For example,

$ cvs -z4 up -dAP
cvs update: Updating .
cvs update: Updating cfg
cvs update: closing down connection to cvs.example.com

$ cvs -z4 ci -m "test commit" test.sh
/cvsroot/bin/cygwin/test.sh,v  <--  test.sh
new revision: 1.25; previous revision: 1.24
cvs commit: closing down connection to cvs.example.com: No such file
or directory

Probably, there are more.

$ cygcheck -c cvs
Cygwin Package Information
Package              Version        Status
cvs                  1.11.22-1      OK

-- 
...Bye..Dmitry.

--
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/