X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Message-ID: <4B263746.3050302@byu.net> Date: Mon, 14 Dec 2009 06:01:58 -0700 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?] References: <26753996.post@talk.nabble.com> <20091212024903.GA3452@KCJs-Computer> <4B250DEB.2060508@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to David Antliff on 12/13/2009 9:46 PM: > For the record, core.autocrlf=true on Cygwin is an absolute PITA ;) I personally haven't ever taken time to notice whether that is the upstream default (if so, it is wrong, IMNSHO), because I have always manually overridden it to core.autocrlf=false. I have a binary mount point because I _want_ binary reproducability, not because I want the DVCS to munge newlines behind my back. So if this is indeed the default, then we should bug the upstream git list to fix their broken behavior, and I will work on looking into changing the default for the next time I package git for cygwin. > 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 :) The upstream git list may be a better list to complain at, since they are the folks that implemented whitespace munging in the first place. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@byu.net volunteer cygwin git maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksmN0YACgkQ84KuGfSFAYA+QQCeMhNBjKVeXeu6Tk8CnwJt/I0s Q6MAoK+6thZDVUNwjIShLOq6FeVXuWyQ =fSa/ -----END PGP SIGNATURE----- -- 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