Re: fixing files committed with wrong eol-style

[...]
> On Unix, a script with CR-LF is really unlikely to work,
> either with Bash, Perl or others...

I will take your word for this, but this:

> The same way a .bat script on Windows fails if LF.

is no longer true (XP+, not tested earlier) - or at least not
100% true, there may be situations I have not come across that
still cause issues. (This could inspire a comment about
Windows attempting to learn from it's past mistakes so why
isn't *nix, but people may get the impression that I'm a
Microsoft fan and that is not true either.)

[...]
> So the end-of-line problem is really simple compared to
> encodings. And with developpers all around the world working
> on the same codebase, it is difficult to check/enforce
> everyone use the "right tool" with the proper configuration
> on any platform.

Everyone's projects have their own problems. I am not about
to tell anyone that using only LF is always safe for all
projects, my only contention was that it can be safe for some,
that EOL issues are not what they once were (at least not on
Windows).

-- 
Geoff Worboys
Telesis Computing