X-Spam-Check-By: sourceware.org
Date: Sat, 28 Jan 2006 09:52:00 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problems with cygwin cvs over ssh.
Message-ID: <20060128085200.GB15572@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <ad2655cb0601250431w10c79e29t AT mail DOT gmail DOT com> <dr8moj$3le$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0601251554180 DOT 839 AT access1 DOT cims DOT nyu DOT edu> <dr8r9d$mcs$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0601251653430 DOT 839 AT access1 DOT cims DOT nyu DOT edu> <dr927o$h87$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0601251907330 DOT 839 AT access1 DOT cims DOT nyu DOT edu> <dre28b$3et$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0601271635150 DOT 27873 AT access1 DOT cims DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0601271635150.27873@access1.cims.nyu.edu>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Jan 27 17:01, Igor Peshansky wrote:
> Ugh, top-posting...   Reformatted.
> 
> On Fri, 27 Jan 2006, Frank-Michael Moser wrote:
> 
> > Igor Peshansky wrote:
> >
> > > The problem is with the CVS server running on Cygwin.  CVS in client
> > > mode works just fine.
> >
> > I have encountered the same problem, have investigated it a bit and came
> > out with two interesting facts:
> >
> > A) Without changing anything else than replacing cygwin1.dll, using the
> > snaphot cygwin1-20050928.dll works fine while using cygwin1-20050929.dll
> > produces the problem.
> >
> > B) Also without changing anything else than replacing cygwin1.dll, using
> > the snaphot cygwin1-20050928.dll "mkdir /tmp/foo/." runs fine while with
> > cygwin1-20050929.dll you see:
> >
> > > $ mkdir /tmp/foo/.
> > > mkdir: cannot create directory `/tmp/foo/.': No such file or directory
> 
> Right.  I missed the "." in the original message.  The change that
> prompted this behavior seems to be
> <http://cygwin.com/ml/cygwin-cvs/2005-q3/msg00224.html>.  I'm assuming the
> motivation for this patch was to duplicate Linux's behavior (which doesn't
> allow trailing "." in a path passed to mkdir).

Indeed.  Eric mentioned that the coreutils testsuite tests thsi behaviour
explicitely.  Since there's not much impact speedwise, we just added
appropriate checks to be POIX compatible here.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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