Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
From: David Rees <d.rees.l@usa.net>
To: cygwin@cygwin.com
Subject: Re: patch problem with forward/backward slashes in patch file
Date: Wed, 07 Mar 2001 16:51:37 -0800
Message-ID: <ukldats967ca5jfcqg7eevrc2t0m8323oa@4ax.com>
References: <kh2bat4jjv8j6e1vtgdq6jrsj8s02o4co2@4ax.com> <4nrbat4k7l19ndugn851cro7072ai9ftqt@4ax.com> <20010307111525.E18117@redhat.com> <329dat08cnf9q6i137l3udjhe0di2ehpd5@4ax.com> <20010307170352.B30908@redhat.com>
In-Reply-To: <20010307170352.B30908@redhat.com>
X-Mailer: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA07298

On Wed, 7 Mar 2001 17:03:52 -0500, Christopher Faylor wrote:

>On Wed, Mar 07, 2001 at 01:29:23PM -0800, David Rees wrote:
>>On Wed, 7 Mar 2001 11:15:25 -0500, Christopher Faylor wrote:
>>>On Wed, Mar 07, 2001 at 12:19:29AM -0800, David Rees wrote:
...
>>
>>Your explanation makes sense, but shouldn't it be using the cygwin DLL
>>to recognize that its directory path? Its obviously using the cygwin
>>DLL to access the file.
>
>Cygwin uses the Windows API to do everything.  Cygwin doesn't go out of
>its way to disallow Windows paths.  When patch passed the backslashed
>file to cygwin, it happily passed it along to the correct Windows function
>bypassing any translation to a "UNIX-like" path.
>

My thought was actually the reverse, that patch should somehow consult
with the filesystem (i.e cygwin) to see if a given string is a
relative path rather than somehow figuring it out itself. However, in
retrospect that would require that cygwin has this API and also
changing patch which I assume is avoided when possible for cygwin
ports?

>>
>>Maybe its a version issue? Anyway, the obvious solution is always use
>>-p0.
>
>I don't think so.  I have never seen patch behave in this fashion.  It
>doesn't work this way on Linux, AFAICT.
>

Fair enough (the diffutils manual is dated 1993). Should I try and
report it somehow? I have no idea where to report GNU doc bugs.

thx,

d

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

