EOL extension

[Dirkjan Ochtman]

On Tue, Dec 1, 2009 at 05:16, Mark Hammond <mhammond at skippinet.com.au> wrote:
> I did.  I cloned and installed it, then read the docs and started to think
> about how I can use it with the hg-based project I work on every day.  I'm
> the only Windows developer on this project, and the text editors my
> colleagues use are dumber than the ones I use, so mixed EOL chars in a
> single file is not unusual.  I then sent a mail outlining how I could see it
> working in such an environment - looking for a way the repository could be
> configured once, and the developers using these other operating systems will
> (a) remain blissfully unaware of EOL issues while (b) no longer introducing
> mixed EOL chars in the repo.  Oh - and (c), so I don't need to be as
> vigilant in my own workflows - even though I painfully strive to keep the
> EOL style consistently \n in that repo, I still make mistakes.

Mark, thanks for working with us on this. 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 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.

Cheers

Dirkjan