Alternatives to EOL extension

Carsten Fuchs carsten.fuchs at cafu.de
Thu Jan 15 14:54:29 UTC 2015


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)?

Best regards,
Carsten



More information about the Mercurial mailing list