From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1374542180.2061.92.camel@joe-AO722> Subject: Re: mistakes in code vs. maintainer flow mistakes From: Joe Perches To: Li Zefan Cc: Sarah Sharp , Ingo Molnar , Linus Torvalds , Guenter Roeck , Greg Kroah-Hartman , Steven Rostedt , Dave Jones , Linux Kernel Mailing List , Andrew Morton , stable , Darren Hart , Rusty Russell Date: Mon, 22 Jul 2013 18:16:20 -0700 In-Reply-To: <51EDD76B.5050407@huawei.com> References: <20130715180403.GD15531@xanatos> <20130715184642.GE15531@xanatos> <20130715195316.GF15531@xanatos> <20130715204135.GH15531@xanatos> <20130718103907.GC23558@gmail.com> <20130718160754.GC5440@xanatos> <20130719092256.GC25784@gmail.com> <20130719190127.GA12990@xanatos> <51EDD76B.5050407@huawei.com> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Tue, 2013-07-23 at 09:07 +0800, Li Zefan wrote: > > Perhaps what might help here is a kernel organizational chart. [] > the complete chart will in no doubt break 80 > characters limit. Actually as the hierarchy is quite flat, I can't > image how long the longest line will be. I think it really doesn't matter unless you want to generate that from the same information that is available via git, scripts/get_maintainer.pl and the MAINTAINERS file.