From: David Brown <davidb@codeaurora.org>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: David Brown <davidb@codeaurora.org>,
Richard Kuo <rkuo@codeaurora.org>, Arnd Bergmann <arnd@arndb.de>,
linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hexagon: Use resource_size function
Date: Thu, 10 Nov 2011 07:28:25 -0800 [thread overview]
Message-ID: <20111110152825.GA13341@huya.qualcomm.com> (raw)
In-Reply-To: <1320914364.20155.10.camel@localhost.localdomain>
On Thu, Nov 10, 2011 at 09:39:24AM +0100, Thomas Meyer wrote:
> Am Dienstag, den 08.11.2011, 17:02 -0800 schrieb David Brown:
> > Some minor nits about the formatting of the patch.
> >
> > On Tue, Nov 08, 2011 at 07:49:30PM +0100, Thomas Meyer wrote:
> > > From: Thomas Meyer <thomas@m3y3r.de>
> >
> > Shouldn't need a From: line, since it is the same as the email you
> > sent it from.
>
> So do I need a From: line or not?
>
> Documentation/SubmittingPatches says:
>
> The "from" line must be the very first line in the message body,
> and has the form:
>
> From: Original Author <author@example.com>
>
> The "from" line specifies who will be credited as the author of the
> patch in the permanent changelog. If the "from" line is missing,
> then the "From:" line from the email header will be used to determine
> the patch author in the changelog.
>
> MUST in the meaning of RFC2119, means it is an absolut requirment. What
> should I do?
The absolute requirement is that the from line must be the first line
in the message body. The "If the 'from' line is missing" even
suggests that it is optional. I agree that the wording isn't all that
great.
I don't believe it hurts anything to use it, it just looks kind of odd
to have a From line that is the same as the originating email address.
You certainly don't need it, given that a vast majority of patches
posted don't contain a from line. Git send-email only generates one
if the author is different from the one sending the message.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-11-10 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 18:49 [PATCH] Hexagon: Use resource_size function Thomas Meyer
2011-11-09 1:02 ` David Brown
2011-11-10 8:39 ` Thomas Meyer
2011-11-10 15:28 ` David Brown [this message]
2011-11-09 5:33 ` rkuo
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=20111110152825.GA13341@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=arnd@arndb.de \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuo@codeaurora.org \
--cc=thomas@m3y3r.de \
/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