Re: [PATCH/RFC 0/3] Per-repository end-of-line normalization

From: Avery Pennarun <apenwarr@gmail.com>
Date: May 6, 2010, 23:38 UTC
Message-ID: <g2m32541b131005061638o8a5e3490x8a5b1c3eb8c73c70@mail.gmail.com>
In-Reply-To: <cover.1273183206.git.eyvind.bernhardsen@gmail.com>

On Thu, May 6, 2010 at 6:27 PM, Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com> wrote:

Show 9 quoted lines

> - An attribute called "auto-eol" is set in the repository to turn on
>  normalization of line endings.  Since attributes are content, the
>  setting is copied when the repository is cloned and can be changed in
>  an existing repository (with a few caveats).  Setting this attribute
>  is equivalent to setting "core.autocrlf" to "input" or "true".
>
> - A configuration variable called "core.eolStyle" determines which type
>  of line endings are used when checking files out to the working
>  directory.

I definitely like this. The existing core.autocrlf setting does cause a lot of confusion for precisely the reason you stated: people often forget to set it until *after* they've checked out the repo, at which time all the files are already checked out wrong and total confusion ensues.

Being able to globally set my preferred eol style in one place, but only have it take effect on projects (and individual files in that project) that we already know have eol constraints, would be wonderful.

Of course this new feature would be in addition to the existing core.autocrlf setting, not replacing it.

This would definitely help our Windows users at work.

Have fun,

Avery