EOL extension

[Mark Hammond]

On 1/12/2009 6:53 PM, Dirkjan Ochtman wrote:

> Mark, thanks for working with us on this.

No problem - I hope I am actually helping.

> I'm afraid it's quite hard
> to appreciate the problems that come up in the kind of scenario you
> describe, but we're trying very hard to make the new eol extension as
> frictionless as possible.

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.

> I was just wondering, do you also have server-side hooks on your work
> project (I'm assuming that's Raindrop, BTW) that force the line
> endings? It seems like that would still help prevent stupid mistakes
> from everyone.

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?

Cheers,

Mark