Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sat, 5 Mar 2005 22:21:35 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bug diff 2.8.7: Separate dir
Message-ID: <20050306032135.GA6714@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20050306014821 DOT 3C2D721016A AT warserver DOT warande DOT net> <422A7110 DOT 84D428B AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <422A7110.84D428B@dessent.net>
User-Agent: Mutt/1.4.2.1i

On Sat, Mar 05, 2005 at 06:55:12PM -0800, Brian Dessent wrote:
>I don't know enough about Cygwin history or internals to say why this is
>the case.  Someone who knows more about it would have to explain it. 
>And as you've seen it can lead to confusing situations.

I'm not sure how an explanation would help and *I'm* not interested in
getting dragged too deeply into this discussion.  It has all of the earmarks
of quickly devolving into cygwin standard discussion #7 where we all learn
that cygwin should try harder to accommodate things that it was designed to
mask or the universe as we know it will implode.

There are some simple facts here.

There isn't going to be any work on diff to deal with this behavior and
there isn't going to be a new cygwin release which changes binmode
behavior.

In other words: the OP should use POSIX paths.

If that isn't acceptable then maybe a native windows version of diff
would work better.  There are certainly at least a couple of those out
there, not that discussion of a native windows version would be
appropriate for this list.

cgf

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