Alternatives to EOL extension

[Mads Kiilerich]

On 01/15/2015 03:54 PM, Carsten Fuchs wrote:
> Hi all,
>
> many thanks for everyone's answers!
>
> Thinking more about it, if I understand you all right, the proper 
> alternative to the EOL extension is to, for example, write a custom 
> script that checks our source code, e.g. for proper EOL style, 
> trailing whitespace, character encoding, and so on, and then for us 
> (the crucial step!) to treat this source code "check" script very much 
> like the source code "build" script. That is, like we'd not commit any 
> changes that don't built, we'd not commit changes for which the 
> "check" script fails.
>
> Would you say that this understanding is principally correct 
> (especially wrt. Mercurial best practices / its "last resort" EOL 
> extension)?

Yes, pretty much. The line ending is a minor thing you easily can 
detect/fix when you are checking/fixing other and bigger things.

/Mads