Alternatives to EOL extension

[Mads Kiilerich]

On 01/14/2015 03:40 PM, Carsten Fuchs wrote:
> 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?

The alternative is to teach your users that they should pay attention to 
what they commit, and that you should review everything carefully anyway 
and reject anything that doesn't comply to your standards.

But if you are working cross platform in a "we trust everybody" 
environment then it makes a lot of sense to use the EOL extension. It 
works quite well and prevents a lot of noise in the repository.

/Mads