From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: Format of patches Date: Thu, 15 May 2014 09:37:53 -0700 Message-ID: <5374ED61.8050804@infradead.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: cpufreq-owner@vger.kernel.org To: Viresh Kumar , Mikulas Patocka Cc: "cpufreq@vger.kernel.org" , Linux Kernel Mailing List , "Rafael J. Wysocki" , "linux-pm@vger.kernel.org" List-Id: linux-pm@vger.kernel.org On 05/15/2014 07:00 AM, Viresh Kumar wrote: > On 15 May 2014 18:15, Mikulas Patocka 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