From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933153AbdGTBFF (ORCPT ); Wed, 19 Jul 2017 21:05:05 -0400 Received: from smtprelay0225.hostedemail.com ([216.40.44.225]:42488 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932107AbdGTBFE (ORCPT ); Wed, 19 Jul 2017 21:05:04 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::,RULES_HIT:41:355:379:541:560:599:973:982:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1777:1792:2198:2199:2393:2559:2562:2828:2892:3138:3139:3140:3141:3142:3353:3622:3653:3654:3865:3866:3867:3868:3870:3872:3874:4321:5007:6691:7875:7903:9010:10004:10400:10450:10455:10848:11232:11658:11914:12050:12663:12740:12760:12895:13069:13161:13229:13311:13357:13439:14093:14096:14097:14659:14721:19904:19999:21080:21324:21450:21627:30029:30054:30075:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: seat04_664281b192908 X-Filterd-Recvd-Size: 2518 Message-ID: <1500512701.25934.47.camel@perches.com> Subject: Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering From: Joe Perches To: Linus Torvalds , Andrew Morton Cc: Randy Dunlap , LKML Date: Wed, 19 Jul 2017 18:05:01 -0700 In-Reply-To: References: <20170719144457.8b1b6556fc7883ac7bc2b2b0@linux-foundation.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.6-1ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2017-07-19 at 17:08 -0700, Linus Torvalds wrote: > I can easily just look at the reject and fix it, but I don't really > want to. Why? Because I hate the MAINTAINERS file. > > It's the most painful file for merging too, because everybody touches > it - kind of like the old "one single Kconfig file" was back in the > bad old days. > For example, just during this merge window: > > $ git rev-list --count --no-merges v4.12.. MAINTAINERS > 112 > > and while most of them obviously didn't cause any conflicts (there > were four this cycle), it's still my least favourite "stupid work". > That file pretty consistently gets 100+ changes to it: > > v4.1: 87 > v4.2: 109 > v4.3: 94 > v4.4: 91 > v4.5: 118 > v4.6: 98 > v4.7: 112 > v4.8: 121 > v4.9: 128 > v4.10: 135 > v4.11: 78 > v4.12: 127 > > So I'm wondering if > > (a) we could add a script to do the alphabetical ordering properly. > > (b) we could split this thing up some sane way. > > Anybody got any ideas? > > I'm throwing out _one_ idea: split it up by the main F: line, so that > maintainership information ends up being hierarchical like the Kconfig > files. Teach "get_maintainer.pl" to just do "find . -name > MAINTAINERS" instead? Just for ease of manipulation and not breaking the script much, I'd suggest just having a MAINTAINERS directory and stuffing each of the sections into separate files. The script would only need to add $ cat MAINTAINERS/* as input.