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: <4B263746.3050302@byu.net> References: <26753996 DOT post AT talk DOT nabble DOT com> <20091212024903 DOT GA3452 AT KCJs-Computer> <4B250DEB DOT 2060508 AT gmail DOT com> <4B263746 DOT 3050302 AT byu DOT net> Date: Wed, 16 Dec 2009 12:53:20 +1300 Message-ID: Subject: Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?] From: David Antliff To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Tue, Dec 15, 2009 at 02:01, Eric Blake wrote: > 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. Ok, I posed a question or two there: http://thread.gmane.org/gmane.comp.version-control.git/135305 I'm really starting to wonder if core.autocrlf=true was such a good idea. It's going to be really hard to switch back if the evidence suggests I should. -- 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