Message-ID: <1490249276.2041.19.camel@perches.com>
Subject: Re: [PATCH] checkpatch: Flag spam header (X-Spam-Report) to prevent
 spurious warnings
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>
Date: Wed, 22 Mar 2017 23:07:56 -0700
In-Reply-To: <20170323060133.GD17578@localhost.localdomain>
References: <1490113805-9295-1-git-send-email-warthog9@eaglescrag.net>
         <1490121068.2041.13.camel@perches.com>
         <20170322152539.GA11892@localhost.localdomain>
         <1490206653.2041.17.camel@perches.com>
         <20170323060133.GD17578@localhost.localdomain>
Content-Type: text/plain; charset="ISO-8859-1"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 475
Lines: 8

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.