----- Original Message ----- > From: "Dmitry Potapov" <dpotapov@xxxxxxxxx> > Sent: Wednesday, May 25, 2011 1:58:33 PM > Subject: Re: Git EOL Normalization > > > Â1) what is the actual text file detection algorithm? > > Â2) what is the autocrlf LF/CRLF detection algorithm? > > Â3) how does autocrlf handle mixed line endings? (either in the > > Âworking copy or repo) > > Currently, the following heuristics are used: > > A file is considered as text if it does not have '\0' or a bare CR, > and the number of non-printable characters is less than 1 in 128. > > Non-printable characters are DEL (127) and anything less than 32 > except CR, LF, BS, HT, ESC and FF. > > Also, to avoid problems with autocrlf=true when someone has already > put a text file with CRLF, CRLF->LF conversion happens only if the tracked > file in the index does not have any CR. > > PS I wrote this mostly from my memory, so I could miss some detail. Thanks! This is very helpful. Stephen -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html