EOL extension

[Dirkjan Ochtman]

So to go back a little bit,

On Mon, Nov 30, 2009 at 23:30, Mark Hammond <mhammond at skippinet.com.au> wrote:
> than it is helping - as do all my attempts at helping with this - so I'm
> happy to leave you guys to it and once some real Windows developers start
> making noise that it does indeed work, I'll look forward to becoming yet
> another happy user.

Yeah, so I'm afraid you have to be that real Windows developer, since
few other people (even among the Windows dev crew we have here!)
experience problems AFAICT, though we did introduce the patch.eol
setting in 1.3 which should help a bunch of cases (does that need to
be integrated with the eol extension more?). We can write code to
solve concrete issues, and we'd be happy to do that; but we don't have
the repository or community to reproduce the problems you're seeing,
and so we can't experience those problems. So, at this point, do you
have *concrete* suggestions for the eol extension?

> An off-the-wall solution may simply be to make hg totally EOL agnostic - ie,
> for "hg diff" etc to only report/operate on the actual changes, ignoring any
> EOL changes which may have been made?  Obviously this goes beyond the
> obvious 'diff' (eg, merging), so I expect this would turn out to be
> non-trivial - but is the effective outcome I am after.

That won't fly; VCS will probably always mostly treat files as
sequences of bytes.

As for the hooks thing, if you write hooks anyway (for use at the
server), it would be easy to also use them as client-side commit hooks
for some of your local repositories.

Cheers,

Dirkjan