linux-kernel - Re: Format of patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5374ED61.8050804@infradead.org>
Date:	Thu, 15 May 2014 09:37:53 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Viresh Kumar <viresh.kumar@...aro.org>,
	Mikulas Patocka <mpatocka@...hat.com>
CC:	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: Re: Format of patches

On 05/15/2014 07:00 AM, Viresh Kumar wrote:
> On 15 May 2014 18:15, Mikulas Patocka <mpatocka@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/