X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B250DEB.2060508@gmail.com>
References: <26753996 DOT post AT talk DOT nabble DOT com> 	 <20091212024903 DOT GA3452 AT KCJs-Computer> 	 <db95995b0912130055r762e443ucb43fe5041ab5f33 AT mail DOT gmail DOT com> 	 <4B250DEB DOT 2060508 AT gmail DOT com>
Date: Mon, 14 Dec 2009 17:46:10 +1300
Message-ID: <db95995b0912132046s2ef1d07docfd1a137cea6e08d@mail.gmail.com>
Subject: Re: Cygwin git - Configuration Problem? [was Re: BASH Shell -  	Configuration Problem?]
From: David Antliff <david DOT antliff AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mon, Dec 14, 2009 at 04:53, Dave Korn
<dave DOT korn DOT cygwin AT googlemail DOT com> wrote:
> David Antliff wrote:
>
>> I've set this in Cygwin.bat and used it successfully to allow users to
>> run bash scripts that are in DOS text-file format. This turns out to
>> be really important when using git with core.autocrlf=3Dtrue...
>
> =A0Say, do you mean "This turns out to be really important when using nat=
ive
> win32 git instead of cygwin git", or do you mean that cygwin git use CRLF=
 as
> the system's default eol rather than LF as it probably ought?

Hmm, I hadn't thought of it like that, but I suppose what I mean is
that "cygwin git uses CRLF as the system's default eol".

So to doubly-confirm: I'm using Cygwin-1.5's git and text files appear
after a fresh clone with CR characters. Same behaviour with
Cygwin-1.7's git-1.6.4.2.

But I'm not sure what the implications are of changing this though. I
just know that we couldn't get bash scripts to work properly until we
made this igncr setting for everyone. I seem to recall it wasn't
consistently broken either, but it certainly threw a spanner in the
works until I discovered that igncr setting.

For the record, core.autocrlf=3Dtrue on Cygwin is an absolute PITA  ;)

Hmm, actually, maybe you can help me work out why a file with trailing
whitespace on the end of one or more lines causes cygwin's git to flag
the file as locally modified when the file hasn't been touched at all.
A 'git diff' shows the entire file as being different, due to the line
endings switching over. Most annoying. I can write more if you're
interested and want to hear about it :)

-- David.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple