Amit Choudhary [off-list ref] writes:
Is it possible that git complains about everything that has ^M in it
and rejects it (that is without trying to fix it, etc.)
I am not sure what you mean. Are you asking if there is a mode
(e.g. command line switch) to tell "git am" to reject any input with
CR in it? I do not think there is, and I do not think it would help
all that much. But perhaps the pre-applypatch hook can be used to
inspect the current working tree files (and it can compare them with
HEAD to learn what are the proposed changes) and reject the patch---
an advantage of such an approach is that the "inspect" step does not
have to be limited to "does it contain a carriage-return?"
Or are you asking if the patch (mis)application that triggered this
discussion thread was somehow caused by Git that complains a payload
with CR in it? I do not think so.