"Neal Kreitzinger" <neal@xxxxxxxx> writes: > I see that the pre-commit.sample reject introduction of lines with trailing > whitespaces. Is there a way to have it reject changes in EOL format (CRLF > vs LF)? Well, from description of relevant config variable, namely `core.whitespace` it looks like by default `trailing-space` with `cr-at-eol` not enabled (default) treats adding CR in LF -> CR LF change as whitespace error. I don't think there is anything *canned* (out of the box) for the change in reverse direction. -- 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