[MERGE] integrated EOL conversion support

[Alexander Belchenko]

Ian Clatworthy пишет:
> Alexander Belchenko wrote:
>> Ian Clatworthy пишет:
>>> I'd greatly appreciate it if someone could apply this patch
>>> on Windows, run "./bzr selftest test_eol" and confirm all
>>> the tests pass there.
>> C:\work\Bazaar\mydev.packs\bzr-eol>python bzr --no-plugins selftest
>> test_eol -v > test.log
>> tests passed
> ....
> ---------------------------------------------------------------------
>> Ran 18 tests in 16.654s
>>
>> OK
>> 12 tests skipped
> 
> Excellent! Thanks. As one of the primary users looking for this,
> I'd be grateful for a review and/or feedback.

OK.

> Thinking out loud, I wonder whether "windows" would be a better
> choice than "dos"? I'm probably showing my age by using the latter.

I'd prefer 'CRLF' and 'LF' instead of 'dos' and 'unix'. Although I'm a bit
younger than you, I remember the dos machines and actualy working on them in 1990s,
so 'dos' name is actually OK for me, and a bit shorter than 'windows', and has
more broad context IMO.

Looking at wikipedia (http://en.wikipedia.org/wiki/Newline)
one can see CRLF was used not only in Microsoft products, but some others.
Although today dos/windows is more known brands.

> I'm also considering adding a value called "clean". That would work
> exactly like "exact" except it would warn if mixed line-endings
> were found in a file. What do you think? Git has something like this
> so I gather it's of value to users.

I think it makes sense. Especially when people want to clean their hairy files.