EOL extension

[Nicolas Dumazet]

2009/12/2 Colin Caughie <c.caughie at indigovision.com>:
> It seems that this would still be a problem with the new extension, because we would still be relying on each user to enable the extension in their .hgrc/mercurial.ini file. But I can't see a way out of that without modifying the core hg code.
>
> The ideal scenario would of course be to eventually integrate this functionality into the core package (obviously it wouldn't do anything if you didn't have a .hgeol file) but I would anticipate some resistance to that idea. The only other idea I can think of would be to have some way for a repository to indicate that it requires a certain extension to be enabled before it can be used, and for hg to disallow commits until it was.

Couldn't agree more.

Someone correct me if I'm wrong, but I think that the original plans
were to integrate this extension in core as soon as it's stable. It
would solve that problem.
Afterall, as you pointed it, either there's an .hgeol and everyone
should comply to the rules, or there's no such file and having the
behavior in core does not change a thing. This would be analog to the
current .hgignore usage.

And if there is some serious resistance to the idea of taking into
account a .hgeol if there is one (?), we could easily code an option
to desactivate this behavior on a per-repo basis. It's much better to
desactivate on-demand instead of activating on-demand.

-- 
Nicolas Dumazet — NicDumZ