Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]
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
Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]
-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 e...@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
Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]
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=true... Say, do you mean This turns out to be really important when using native 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? cheers, DaveK -- 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
Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]
On Mon, Dec 14, 2009 at 04:53, Dave Korn dave.korn.cyg...@googlemail.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=true... Say, do you mean This turns out to be really important when using native 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=true 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
