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: <4.3.1.2.20021119131134.01754d48@pop.rcn.com> X-Sender: lhall AT pop DOT rcn DOT com Date: Tue, 19 Nov 2002 13:14:58 -0500 To: Parish , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: patch(1) (Win32) and path separators In-Reply-To: <3DDA7E9A.2010603@ntlworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 01:10 PM 11/19/2002, Parish wrote: >patch(1) on Win32 seems to insist on '\' rather than '/' in the paths in diffs. This is somewhat at odds with diff(1) which uses '/', even on Windows. > >According to the manpage there is no option to change this behaviour. > >I have d/l the sources but have yet to build it (am I correct that it needs gcc to build, i.e. won't build with MSVC++?) with the intention of making my own version that works with '/'. > >Can anyone confirm that there isn't an undocumented option (cmd line or build) to make it use '/'? If there isn't, why is it that the Windows version works this way, especially when diff(1) DTRT? What patch are you using? The Cygwin version works fine with '/'. I have to assume that since you mention the "Windows version" that your talking about a native port and not the patch that's available through Cygwin. If that's a proper assumption, you don't have the right forum to discuss the Windows native version of patch. This list discusses Cygwin-related issues only. Sorry, Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/