FW: Re: EOL: patch.eol=auto setting

[alexrayne]

> Martin Geisler пишет:
>>> Maybe this unstable work caused of error on parsing .hgeol? What
>>> happen if parsing of some string\rules failed?
>>>     
>>
>> Why don't you just try it? Commit a .hgeol file with a syntax error and
>> you'll get this:
>>
>>   % hg status
>>   hg: config error at .hgeol:3: '='
>>
>> You'll actually not be able to commit a fixed .hgeol file unless you
>> disable the extension... hmm, we better fix that :-)
>>
>> Using unknown keywords like "**.txt = foo" is silently ignored, we
>> should fix that as well.
>>
>> 

> i cant beleave that you checkout .hgeol every time for take hgeol
> setting, i suspect you use working copy of .hgeol,
> so why you need commiting one? just for sure?
> it makes problematic changing it, and setting up it contents for 1st
> use. this rigours can scare away users from hgeol.
> imho it is native and simpler to deliver care on it to repository user
> and at present use working file as is until appeared
> some handy and stable strategy of commiting it.
> you have more important tasks to do, then work with this one.

imho, at least for simplify debugging hgeol better to provide some
setting (maybe in hgrc) that turn off checking that .hgeol under version
control.