X-Spam-Check-By: sourceware.org Message-ID: <43A20542.1050405@student.lu.se> Date: Fri, 16 Dec 2005 01:07:30 +0100 From: Lennart Borgman User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) MIME-Version: 1.0 To: Dave Korn CC: cygwin AT cygwin DOT com, Emacs Devel , Eli Zaretskii Subject: Patch and Cygwin References: <43A1ACC1 DOT 9090805 AT student DOT lu DOT se> <43A1B2A1 DOT 2020907 AT student DOT lu DOT se> In-Reply-To: <43A1B2A1.2020907@student.lu.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 This is a summary of my tests with Cygwin patch and different line ending styles. (Only LF and CRLF are tested here.) I have downloaded patch 2.5.9 from ftp://alpha.gnu.org/gnu/diffutils/patch-2.5.9.tar.gz and compiled it using Cygwin. I have used this patch and the patch that currently comes with Cygwin to do some tests of patch and diff when the files to compare and patch have different line ending styles. I have also made this test using MSYS and GnuWin32 utilities. The result is that the only option that seems to be able to handle the mix of line endings is Cygwin using DOS line endings with patch 2.5.9. (The only thing that did not work was preservation of line endings in the patched file, but that seems to be a small problem here.) To see more of the result see here: http://ourcomments.org/GNU/patchcrlf/readme.txt Lennart Borgman wrote: > After finishing the installation of gcc-core (which includes binutils > as far as I understand) configure + make ran fine. I have now patch > 2.5.9 compiled for Cygwin I believe. Or? > > My intention was to look at the source code and see how it handles > line endings. I do not know if that is realistic though. As I said > before what I want it to do is: > > 1) Keep the line end style for the patched file. > > 2) Read the patch file and apply it even if it uses a different line > end style. > > This is simply what I expect of a text oriented tool. Comments and > help are welcome! (But please no holy war on line end style. That is > just improductive.) -- 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/