This is the mail archive of the
mailing list for the Cygwin project.
Re: Problems with cygwin cvs over ssh.
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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html