From: Joe Perches <joe@perches.com>
To: Darren Hart <dvhart@infradead.org>
Cc: "John 'Warthog9' Hawley (VMware)" <warthog9@eaglescrag.net>,
linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] checkpatch: Flag spam header (X-Spam-Report) to prevent spurious warnings
Date: Wed, 22 Mar 2017 23:07:56 -0700 [thread overview]
Message-ID: <1490249276.2041.19.camel@perches.com> (raw)
In-Reply-To: <20170323060133.GD17578@localhost.localdomain>
On Wed, 2017-03-22 at 23:01 -0700, Darren Hart wrote:
> I still haven't figured out why we test for this specific set of patterns. Why
> is a line that starts with a space and ends with a newline considered still
> in_header_lines. Or more specifically, why aren't we just testing for an empty
> line (RFC 5322 Section 2.1, defining the separation of headers and the body).
Because of the From: and commit: lines sometimes used to describe
patches sent on behalf of others.
next prev parent reply other threads:[~2017-03-23 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:30 [PATCH] checkpatch: Flag spam header (X-Spam-Report) to prevent spurious warnings John 'Warthog9' Hawley (VMware)
2017-03-21 18:31 ` Joe Perches
2017-03-22 15:25 ` Darren Hart
2017-03-22 18:17 ` Joe Perches
2017-03-23 6:01 ` Darren Hart
2017-03-23 6:07 ` Joe Perches [this message]
2017-03-24 20:14 ` John 'Warthog9' Hawley
2017-03-24 20:19 ` John 'Warthog9' Hawley
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=1490249276.2041.19.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog9@eaglescrag.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.