Re: crlf with git-svn driving me nuts...

[Dmitry Potapov <dpotapov@gmail.com>]

On Wed, Apr 16, 2008 at 03:56:18PM -0500, Martin Langhoff wrote:
> On Wed, Apr 16, 2008 at 3:01 PM, Dmitry Potapov <dpotapov@gmail.com> wrote:
> >  core.autocrlf=false is a bad choice for Windows.
> ...
> >  If you do not want problems, you should use core.autocrlf=true
> >  on Windows.
> 
> If you are making the above statements in generally about git, I
> disagree.

I stand corrected. It should be either core.autocrlf=true is you
like DOS ending or core.autocrlf=input if you prefer unix-newlines.
In both cases, your Git repository will have only LF, which is the
Right Thing. The only argument for core.autocrlf=false was that
automatic heuristic may incorrectly detect some binary as text and
then your tile will be corrupted. So, core.safecrlf option was
introduced to warn a user if a irreversable change happens. In fact,
there are two possibilities of irreversable changes -- mixed line-ending
in text file, in this normalization is desirable, so this warning can be
ignored, or (very unlikely) that Git incorrectly detected your binary
file as text. Then you need to use attributes to tell Git that this file
is binary.

I have not used git-svn on Windows for some time now, because now I have
a mirror running on Linux, so I clone directly from it.

Dmitry