[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Dec 2016 10:19:06 -0800
From: Joe Perches <joe@...ches.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ben Evans <bevans@...y.com>
Cc: James Simmons <jsimmons@...radead.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Andreas Dilger <andreas.dilger@...el.com>,
Oleg Drokin <oleg.drokin@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lustre Development List <lustre-devel@...ts.lustre.org>
Subject: Re: [PATCH v2 3/5] staging: lustre: headers: sort headers affected
by obdo move
On Mon, 2016-12-12 at 17:34 +0100, Greg Kroah-Hartman wrote:
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Mon, Dec 12, 2016 at 02:42:29PM +0000, Ben Evans wrote:
> > This was done to conform to the Lustre Coding Guidelines.
>
> What is this mythical guidelines, and why does it differ from the kernel
> source ones?
It's not like it's hard to find
http://wiki.lustre.org/Lustre_Coding_Style_Guidelines
And in specific:
http://wiki.lustre.org/Lustre_Style_Guide_Includes
There is no single mandated code style for this.
Some people like reverse christmas tree.
Whatever...
Powered by blists - more mailing lists