Finn Arne Gangstad <finnag@xxxxxxx> writes: > Previously, autocrlf would only work well for normalized > repositories. Any text files that contained CRLF in the repository > would cause problems, and would be modified when handled with > core.autocrlf set. > > Change autocrlf to not do any conversions to files that in the > repository already contain a CR. git with autocrlf set will never > create such a file, or change a LF only file to contain CRs, so the > (new) assumption is that if a file contains a CR, it is intentional, > and autocrlf should not change that. > > The following sequence should now always be a NOP even with autocrlf > set (assuming a clean working directory): > > git checkout <something> > touch * > git add -A . (will add nothing) > git comit (nothing to commit) > > Previously this would break for any text file containing a CR How this feature relates to `core.safecrfl'? -- Jakub Narebski Poland ShadeHawk on #git -- 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