Alternatives to EOL extension

Carsten Fuchs carsten.fuchs at cafu.de
Wed Jan 14 14:40:15 UTC 2015


Dear Mercurial group,

I'm new to Mercurial, and was wondering what the proper way is to handle EOL styles.

http://mercurial.selenic.com/wiki/EolExtension says that the EOL extension is considered 
a feature of last resort.

http://mercurial.selenic.com/wiki/FeaturesOfLastResort says: "These features are all at 
odds with Mercurial's core design, and will therefore always present some difficulties 
in terms of performance, ease of use, and integration. As such, when using them, you 
won't get the best possible Mercurial experience. Due to our compatibility rules, these 
features will continue to exist — but we want to make you aware that there are often 
better alternatives.   You should give careful consideration to alternatives when first 
deploying Mercurial."

But what please are the alternatives?

For my project, it would be ok to use a single EOL style under all platforms, but how 
can I make sure that in a repository (either local development or the remote "central" 
repository) mixed EOL-styles cannot inadvertently be introduced?

Best regards,
Carsten



More information about the Mercurial mailing list