Crazy thought - how about you change your editor to use LF? Operating
systems wars aside, this is clearly a place where Windows borked up.
Andrei
On 1/25/11 3:13 AM, Walter Bright wrote:
Johannes Pfau wrote:
The "core.autocrlf" section on http://progit.org/book/ch7-1.html says:
"Git can handle this by auto-converting CRLF line endings into LF when
you commit, and vice versa when it checks out code onto your filesystem.
You can turn on this functionality with the core.autocrlf setting. If
you’re on a Windows machine, set it to true — this converts LF endings
into CRLF when you check out code"
and
"If you’re on a Linux or Mac system that uses LF line endings, then you
don’t want Git to automatically convert them when you check out files;
however, if a file with CRLF endings accidentally gets introduced, then
you may want Git to fix it. You can tell Git to convert CRLF to LF on
commit but not the other way around by setting core.autocrlf to input"
Here's what happens - someone checks in CRLF files on Windows. Then I
check out the repository on Linux. Now, git status claims that these
files are "different" on Linux and need checking in again.
There really is no hope for this, other than ensuring that all source
files checked in are LF, nor CRLF, terminated.
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
