From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C27F7C433DB for ; Fri, 5 Feb 2021 16:38:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 69DF564E2E for ; Fri, 5 Feb 2021 16:38:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233000AbhBEO7N (ORCPT ); Fri, 5 Feb 2021 09:59:13 -0500 Received: from smtprelay0110.hostedemail.com ([216.40.44.110]:46778 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S232892AbhBEO4E (ORCPT ); Fri, 5 Feb 2021 09:56:04 -0500 Received: from smtprelay.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by smtpgrave07.hostedemail.com (Postfix) with ESMTP id E931418037BD4 for ; Fri, 5 Feb 2021 14:07:16 +0000 (UTC) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay05.hostedemail.com (Postfix) with ESMTP id F32E518020C47; Fri, 5 Feb 2021 14:07:00 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: color19_270d317275e5 X-Filterd-Recvd-Size: 3084 Received: from [192.168.1.159] (unknown [47.151.137.21]) (Authenticated sender: joe@perches.com) by omf08.hostedemail.com (Postfix) with ESMTPA; Fri, 5 Feb 2021 14:06:59 +0000 (UTC) Message-ID: <565bfe3cd09197903ae07a87aadd94d1117d4106.camel@perches.com> Subject: Re: Small student project idea on appropriate integration trees in MAINTAINERS From: Joe Perches To: Lukas Bulwahn , Jonathan Corbet Cc: devel@lists.elisa.tech, Ralf Ramsauer , Wolfgang Mauerer , Linux Kernel Mailing List , Pia Eichinger , =?UTF-8?Q?Ba=C5=9Fak?= Erdamar Date: Fri, 05 Feb 2021 06:06:57 -0800 In-Reply-To: References: <20210128165447.3da0d98e@lwn.net> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.38.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2021-02-05 at 07:42 +0100, Lukas Bulwahn wrote: > On Fri, Jan 29, 2021 at 12:54 AM Jonathan Corbet wrote: > > > > On Fri, 22 Jan 2021 09:22:24 +0100 > > Lukas Bulwahn wrote: > > > > > In this project, we can make use of: > > > > > > - gitdm [git://git.lwn.net/gitdm.git]: gitdm includes some scripts to > > > parse MAINTAINERS and obtain the integration tree patch of a commit. > > > > Look also at the 'treeplot' tool there, which determines which tree(s) > > each patch went through and makes pretty (OK, not hugely pretty) pictures > > from the result. > > Thanks, we are well aware, and that is a good reminder for Basak and > me to get our gitdm treeplot patches in shape for proper submission. > > > > > I suspect you'll find that the tree information is mostly correct. > > Your suspicion, which is counter to my hypothesis, makes this > investigation worthwhile just to see how correct that information > really is. I suspect the specific development trees listed in each MAINTAINERS subsystems is mostly useless information. Just like the number of subsystems listed and their nominal maintainers is more vanity than actual. MAINTAINER subsystems may be active for a small window of time when submitted, but these mostly driver entries are quickly aged out as the typically driver is completed. The 80:20 rule when applied to MAINTAINERS I suspect is more like 90:10. > > Developers need to know that to be able to base their patches properly; an > > incorrect entry would lead to a certain amount of maintainer misery. The -next integration tree works relatively well as the basis for development. If a patch doesn't apply, it's typically fairly easy to rebase it in the rare occasion it doesn't apply to a particular active tree.