From: Randy Dunlap <rdunlap@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Mikulas Patocka <mpatocka@redhat.com>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Format of patches
Date: Thu, 15 May 2014 09:37:53 -0700 [thread overview]
Message-ID: <5374ED61.8050804@infradead.org> (raw)
In-Reply-To: <CAKohpokGQSuts5rr4XeFb1dsykfNX-A--NXapkgJ2g0fUjVmQQ@mail.gmail.com>
On 05/15/2014 07:00 AM, Viresh Kumar wrote:
> On 15 May 2014 18:15, Mikulas Patocka <mpatocka@redhat.com> wrote:
>>>> ---
>>>
>>> Blurb here :)
>>
>> Sure - but if I want you to read "Blurb here :)" before reading the git
>> message, I need to place it at the top of the email, before the git
>> message.
>
> You can't, git will pick it up :)
Right. The patch description goes at the top of the email.
If you want to include text that should not be part of the patch
description, you can put it after the --- or you can put it into
an introductory email (like [PATCH 0/5]).
> And people are trained enough to read stuff at this place as it was
> present over the top of mail :)
--
~Randy
prev parent reply other threads:[~2014-05-15 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 14:24 [PATCH 1/2] speedstep-smi: enable interrupts when waiting Mikulas Patocka
2014-05-14 14:25 ` [PATCH 2/2] speedstep: clean up interrupt disabling Mikulas Patocka
2014-05-15 4:45 ` [PATCH 1/2] speedstep-smi: enable interrupts when waiting Viresh Kumar
2014-05-15 10:37 ` Format of patches (was: [PATCH 1/2] speedstep-smi: enable interrupts when waiting) Mikulas Patocka
2014-05-15 10:45 ` Viresh Kumar
2014-05-15 12:45 ` Mikulas Patocka
2014-05-15 14:00 ` Viresh Kumar
2014-05-15 16:37 ` Randy Dunlap [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=5374ED61.8050804@infradead.org \
--to=rdunlap@infradead.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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).