EOL extension

[Dirkjan Ochtman]

On Tue, Dec 1, 2009 at 09:12, Mark Hammond <mhammond at skippinet.com.au> wrote:
> I expect that one way to appreciate the issues would be to work with a
> repository which uses \r\n line-endings by default on Linux/OSX.  This is
> hard in practice though - to really see the problems, it must be a
> repository shared between a number of people using different EOL
> conventions.  This is a similar problem to trying to test win32text or EOL
> in isolation - the problems only become apparent in real-world usage
> scenarios.

Exactly, it's just hard to synthesize.

> It is raindrop :)  Raindrop is hosted at hg.mozilla.org and I'm not familiar
> with what hooks they make available.  Please excuse my ignorance regarding
> server hooks, but it seems that even if they did offer such a hook, this
> would only apply at *push* time, not commit time.  Given the distributed
> nature of hg (eg, I'm also pushing to a contributor's clone hosted at
> bitbucket) it seems that by the time a server-side hook kicks in, the damage
> has already been done?

Aravind (the guy who manages the hg deployment on hg.m.o) can deploy
all kinds of stuff if you open a bug about it.

Even if the damage has been done, you could commit a new changeset on
top of it, to make sure the (or all branch tips) of the remote repo
always have sane line endings (and I guess the scenario where people
push one self-authored cset at a time is still pretty common). That
still seems like a win to me.

Cheers,

Dirkjan