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

From: Avery Pennarun <apenwarr@gmail.com>
Date: May 6, 2010, 23:54 UTC
Message-ID: <z2k32541b131005061654je98055aanac16e790d412684e@mail.gmail.com>
In-Reply-To: <g2m32541b131005061638o8a5e3490x8a5b1c3eb8c73c70@mail.gmail.com>

On Thu, May 6, 2010 at 7:38 PM, Avery Pennarun <apenwarr@gmail.com> wrote:

Show 5 quoted lines

> 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.

Oh, just to clarify the rationale a bit more:

Whether a developer wants autocrlf or not actually is project-dependent, not user-dependent or "all Windows users want autocrlf." For example, if I'm running Cygwin and I checkout a copy of the git source code to build with Cygwin gcc, I definitely don't want autocrlf. (Actually, almost always, for C source code I don't want autocrlf, or I want autocrlf=input.)

If I'm checking out a copy of our Delphi project on Windows, though, I need autocrlf or the IDE goes bananas. And our team would be happy to put the right magic incantation in a .gitattributes file in our Delphi project if it would make this work out automatically.

Setting core.autocrlf on one of our Windows developers' systems can't cover both of those cases automatically, whereas the settings Eyvind has proposed would solve our problem.

Have fun,

Avery