Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 2 Nov 2000 17:14:51 -0500 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: patch text mode problem with latest CVS source Message-ID: <20001102171451.A15737@redhat.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <20001102151709 DOT A1024 AT dothill DOT com> <20001102152046 DOT B14935 AT redhat DOT com> <20001102154456 DOT B1024 AT dothill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001102154456.B1024@dothill.com>; from Jason.Tishler@dothill.com on Thu, Nov 02, 2000 at 03:44:56PM -0500 On Thu, Nov 02, 2000 at 03:44:56PM -0500, Jason Tishler wrote: >On Thu, Nov 02, 2000 at 03:20:46PM -0500, Christopher Faylor wrote: >> On Thu, Nov 02, 2000 at 03:17:09PM -0500, Jason Tishler wrote: >> >Using the cygwin1.dll that I built from the latest CVS source (as of >> >about 11 AM EST today) causes patch to convert all files actually >> >patched to text mode. Note that I checked and my cygdrive mount is >> >binary so this is not the problem. Has anyone else observed this with >> >CVS or 1.1.5-3? >> >> A better question is if this behavior differs from cygwin 1.1.4. > >Yes, in my experience the behavior differs. In 1.1.4, patched files do >not get converted into text mode, in 1.1.5 they do. If I toggle between >the DLLs and apply the same patch to the same file (or a copy of the >original), the file remains binary in 1.1.4 and converts to text in >"1.1.5". In my experience, patch does exactly the same thing under 1.1.4 and 1.1.5. It seems to be controlled by the value of your "TMP" (or possibly "TEMP") environment variable. If that is set to a directory that is mounted as text, then the resulting file has \r\n line endings. If you can give me a simple test case which illustrates the problem I will investigate it. Please include the cygcheck -r -s -v output for both the failing and succeeding cases. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com