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

["Nigel Magnay" <nigel.magnay@gmail.com>]

>  lose anything and you can set eol=native later. Unfortunately, now SVN
>  users forget to set eol=native a way too often. So, IMHO, Git approach
>  based on heuristic is much better when most of stored files are text.
>

I agree - since the forgetful users includes us!

>
>  > so maybe it's just easier to coax those projects into fixing
>  > their svn repos (but of course it's not really an issue for them, so
>  > it might be a bit of a hard sell).
>
>  If they care about support different platforms then it _is_ issue
>  for them too. On the other hand, if everyone uses Windows with CRLF,
>  you can do that with Git too just by setting autocrlf=false.
>

Actually it seems to be less of an everyday issue- but I think it's
because the diff tools in use by programs downstream are probably
stripping CRs anyway before presenting diffs, so it all 'appears' to
be right. Certainly I've been sharing via a svn repo through Eclipse
with windows users for ages without it being a problem. Either way,
the problem in touched/untouched-files was the majority of my
confusion as I wasn't expecting to find a bug and was assuming I was
doing something wrong...

>
>  >
>  > Yes, in the sense that git is primarily a *nix tool, so it treats LF
>  > as canon
>
>  and perhaps even more important, it is written in C and where LF has
>  always been considered as EOL since the first Hello-World program was
>  written in C:
>
>    printf("Hello world!\n");
>  -----------------------^^
>
>  So, naturally LF is considered as EOL inside of Git. Actually, CVS does
>  so, and even SVN does if you set eol=native.
>
>
>  > and CRLF as somehow 'stupid' (I.E you could make an equally
>  > valid argument for the reverse position, it just depends on your
>  > perspective ;-)) ;
>
>  There is no good technical reason to have two symbols as the end-of-line
>  marker instead of one. Most programs on Windows just remove CR when read
>  from a file and then adding it back before LF when writing it back. So,
>  CR is clearly redundant.
>

Well.... Newline = LF vs CRLF (vs CR for early mac.. erk) dates to
well before C and UNIX; back into the days of baudot codes and
teletype printers that couldn't physically newline in the time taken
for 1 character to be processed; LF is meant to mean Line Feed and CR
is meant to mean "Carriage Return", so CRLF is in that sense quite
logical. But that's standards committees and backwards compatibility
for you :-/