Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <8D98BD395C94D7119DF800306E015966379507@ednex506.dsto.defence.gov.au> From: "Rutten, Mark" To: "'cygwin AT cygwin DOT com'" Subject: RE: cygwin and cvs Date: Wed, 9 Jun 2004 09:28:29 +0930 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" > As far as I know I am running the latest version of cygwin > (1.5.10-3) and cvs (1.11.6-3). As I said in my original > post, I have been using cvs successfully under cygwin for a > while and have only recently (as in the last week or so) > started to experience this problem. I will try debugging > when I have some spare time. It turns out that when I revert back to cygwin version 1.5.9-1 the cvs problem (of being able to remove the #cvs.lock directory)disappears. However this isn't the most satisfying solution. Once again, I'll try debugging when I have some spare time. Mark. -- 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/