Hi,
The clean solution to this issue seems to be documented at http://line-endings.gitrecipes.de/ .
For a quick fix, this would be the way on the Windows machine:
To use:
git config core.autocrlf off git config --global core.autocrlf off
And here's how to apply it, from #git:
_ikke_: You do that after clone. A git reset --hard might be needed to fix the line endings again ojacobson: you'll need to do it in each clone, after cloning; every git-checkout *after* that will use the new setting
So it should look like this:
git clone [Gambit's repo URL] cd [cloned gambit repo dir] git config core.autocrlf off git reset --hard
(or as an alternative to the last line, "git checkout -- ." or "git checkout [branch name]" should deliver too apparently.)
Brgds
2013/4/17 Marc Feeley feeley@iro.umontreal.ca [...]
Yep, differences are in end-of-line encoding, probably due to my git
settings. Didn't catch it because I ran diff as `diff -qw test1.ok test1.out'.
I see. So the file with the cr-lf end-of-line encoding is the test1.ok file, not the test1.out file (which has lf end-of-line encoding reliably on all OSes). I wonder how I could force git to treat test1.ok as a binary file. In fact I don't see how git can be so confident that test1.ok is a text file to change the lf to cr-lf.
Marc
Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list