[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <xmqqk17eyfh1.fsf@gitster-ct.c.googlers.com>
Date: Mon, 02 Dec 2019 06:22:34 -0800
From: Junio C Hamano <gitster@...ox.com>
To: Amit Choudhary <amitchoudhary2305@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
Git List Mailing <git@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"open list\:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Jonathan Neuschäfer <j.neuschaefer@....net>
Subject: Re: [PATCH] Documentation: networking: device drivers: Remove stray asterisks
Amit Choudhary <amitchoudhary2305@...il.com> 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.
Powered by blists - more mailing lists