From: Junio C Hamano <gitster@pobox.com>
To: Amit Choudhary <amitchoudhary2305@gmail.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Git List Mailing" <git@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [PATCH] Documentation: networking: device drivers: Remove stray asterisks
Date: Mon, 02 Dec 2019 06:22:34 -0800 [thread overview]
Message-ID: <xmqqk17eyfh1.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAFzckaEQo6CQM9LukikgbtUKZX=eajG+OFNhnDJ_EY7M1V4XKA@mail.gmail.com> (Amit Choudhary's message of "Mon, 2 Dec 2019 15:20:08 +0530")
Amit Choudhary <amitchoudhary2305@gmail.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.
prev parent reply other threads:[~2019-12-02 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 1:03 Fw: [PATCH] Documentation: networking: device drivers: Remove stray asterisks Jonathan Corbet
2019-12-01 1:20 ` Linus Torvalds
2019-12-01 1:45 ` Jonathan Corbet
2019-12-01 6:35 ` Junio C Hamano
2019-12-01 14:28 ` Linus Torvalds
2019-12-01 15:27 ` Junio C Hamano
2019-12-02 9:50 ` Amit Choudhary
2019-12-02 14:22 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk17eyfh1.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=amitchoudhary2305@gmail.com \
--cc=corbet@lwn.net \
--cc=git@vger.kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).