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 Date: Wed, 5 May 2004 17:50:46 +0300 From: Baurjan Ismagulov To: cygwin AT cygwin DOT com Subject: Re: newline in patch command output Message-ID: <20040505145044.GB20299@ata.cs.hacettepe.edu.tr> Mail-Followup-To: cygwin AT cygwin DOT com References: <20040505125151 DOT GA20299 AT ata DOT cs DOT hacettepe DOT edu DOT tr> <4098F133 DOT FF888288 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4098F133.FF888288@dessent.net> User-Agent: Mutt/1.5.4i X-IsSubscribed: yes Hello, Brian! Thank you for a prompt reply. On Wed, May 05, 2004 at 06:50:43AM -0700, Brian Dessent wrote: > patch is a tricky area in terms of line-endings. This is mostly > explained in . Wow! How did you locate this message? I see it appearing in results for "patch newlines" but not for "patch newline" (I use marc.theaimsgroup.com). > Patch can read in either binmode or textmode (depending on the mount and > presense of --binary) but it always writes its output in binmode, which > is what causes your CRs to go away. So, my only option is having a hacked version of patch that writes with CR? BTW, I've tried also diffing and patching CR/LF terminated trees in Unix mode. Patch failed to apply diff output (it was LF-terminated, IIRC) to a CR/LF-terminated tree. Any idea why? > Corinna might be able to clarify why this must be so. I would greatly appreciate if she does. With kind regards, Baurjan. -- 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/