EOL extension

Mark Hammond mhammond at skippinet.com.au
Tue Dec 1 17:31:58 CST 2009


[Dropping Brett from the CC - I'm sure he can follow on-list if he is 
interested]

On 2/12/2009 10:20 AM, Martin Geisler wrote:
> The old win32text lets you do this to mark all non-binary files as
> native:
>
>    [extensions]
>    hgext.win32text =
>
>    [encode]
>    ** = cleverencode:
>
>    [decode]
>    ** = cleverdecode:
>
> That is the per-user configuration and it's takes straight from the
> documentation. The new eol extension will let you do the same by adding
>
>    [patterns]
>    ** = native
>
> to .hgeol in the repository. Is that not what you're asking for or am I
> being very dense? :-)

That is what I am asking for - thank you!  My first email suggested that 
some people may object to the guessing (IIRC, MvL on python-dev 
objected), so a different spelling might be desired to meet their 
requirements too, but personally I don't care much about that.

Do you have any advice for how to configure things to work with an 
existing repo which already has different EOL conventions between files 
(although assuming each individual file is internally consistent)? 
Should I just list the files with \r\n line endings individually?  If 
so, what 'filter' should I specify?  binary?

Thanks,

Mark


More information about the Mercurial-devel mailing list