EOL extension

[Colin Caughie]

> > I made a first pass at trying to use the eol extension for real.
> I
> > started with a fresh clone of an existing repository.  After
> adding
> > and
> > committing my .hgeol file, I wondered how to convert the working
> > tree to
> > the new format - and figured I could do "hg up -r 0" followed by
> "hg
> > up".  It has since been pointed out I probably wanted '-r null',
> and
> > although I don't get the same problem with '-r null' this problem
> > seems
> > worth reporting anyway.
>
> I also just tried it with one of our own repos. This is a repo that
> has been using win32text, so internally all of its EOLs are LF, but
> in our Windows work areas they are CRLF.
>
> I disabled win32text, added an .hgeol file (also with "**=native"),
> committed it, did "hg up null", then "hg up 6.0" (6.0 being a named
> branch).
>
> Running "hg status" at this point shows several files being marked
> as modified. "hg diff" shows all of the lines in these files as
> having changed. If I run "hg winmerge" on the other hand (I have
> WinMerge configured as an external diff tool), WinMerge reports no
> changes, even though it is configured not to ignore line ending
> differences. Moreover all of the affected files have the correct
> CRLF line endings in my working directory, and I know they are LF in
> the repository.

Quick update on this: I figured out what was wrong. I hadn't put

[repository]
native = LF

in my .hgeol file. Having done that it seems to work.

Colin


Latest News at: http://www.indigovision.com/news2009.php