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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8E1B1C0015E for ; Thu, 27 Jul 2023 00:11:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229776AbjG0AL3 (ORCPT ); Wed, 26 Jul 2023 20:11:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229495AbjG0AL0 (ORCPT ); Wed, 26 Jul 2023 20:11:26 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CFEC919B5 for ; Wed, 26 Jul 2023 17:11:25 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 65B4761CC2 for ; Thu, 27 Jul 2023 00:11:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 777A2C433C8; Thu, 27 Jul 2023 00:11:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1690416684; bh=tKiRxD59OQixQ/evxuII/f2eAwOKeS3mdm+pVnVX+sI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=UXKssJi+hZYTx+FhcYd583PTDvNIviwNYhxHkxMwqnAdHx77jakmR86QYiCdslsPn coI6ChtYTro1hqCsi/GBnakYTVG/RZrmtfiy59meovOLzdsvuDh1flm7dXzAkDDazC BConrzR++XSHeiOkcaUEPoUASdbpj5z2WRG9Ay8G6nrfkiNYtzAN6LYHsuxeq1/sYQ /ud6OX7M2m2zn197b2aSkziC3YNRJqFRYMMLXbzF7zHkIsLcKbd4er8YxubZsBqNqP C9BMPlc3+Od1T0sxGB37Jr3rdcWspbnvyzYEzy9QtHiyCesWb0Qg/RvOpdnUAOC3MU wrH0l44JSvXig== Date: Wed, 26 Jul 2023 17:11:23 -0700 From: Jakub Kicinski To: Konstantin Ryabitsev Cc: Linus Torvalds , Joe Perches , Krzysztof Kozlowski , geert@linux-m68k.org, gregkh@linuxfoundation.org, netdev@vger.kernel.org, workflows@vger.kernel.org, mario.limonciello@amd.com Subject: Re: [PATCH v2] scripts: get_maintainer: steer people away from using file paths Message-ID: <20230726171123.0d573f7c@kernel.org> In-Reply-To: <20230726-june-mocha-ad6809@meerkat> References: <20230726114817.1bd52d48@kernel.org> <20230726130318.099f96fc@kernel.org> <20230726133648.54277d76@kernel.org> <20230726145721.52a20cb7@kernel.org> <20230726-june-mocha-ad6809@meerkat> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: workflows@vger.kernel.org On Wed, 26 Jul 2023 19:47:31 -0400 Konstantin Ryabitsev wrote: > > And have every other subsystem replicate something of that nature. > > > > Sidebar, but IMO we should work on lore to create a way to *subscribe* > > to patches based on paths without running any local agents. But if I > > can't explain how get_maintainers is misused I'm sure I'll have a lot > > of luck explaining that one :D > > I just need to get off my ass and implement this. We should be able to offer > the following: > > - subsystem maintainers come up with query language for what they want > to monitor (basically, whatever the query box of lore.kernel.org takes) > - we maintain a bot that runs these queries and populates a public-inbox feed > - this feed is available via read-only pop/imap/nntp (pull subscription) > - it is also fed to a mailing list service (push subscription) *Nod* > The goal is to turn the tables -- instead of patch submitters needing to > figure out where the patch needs to go (via get_maintainer or similar > scripts), they just send everything to lkml or patches@lists.linux.dev and let > the system figure out who needs to look at them. My initial motivation for this was to let people (who are *not* maintainers) subscribe to parts of netdev. During previous cycles we saw ~246 emails a day. If someone is only interested in e.g. IP routing fishing out the one routing patch a week from all the driver noise is almost impossible. > That's for the part that I was already planning to do. In addition, coming > back to the topic of this thread, we could also look at individual patches > hitting the feed, pass them through any desired configuration of > get_maintainer.pl, and send them off any recipients not already cc'd by the > patch author. I believe this is what you want to have in place, right, Jakub? Hm, hm. I wasn't thrilled by the idea of sending people a notification that "you weren't CCed on this patch, here's a link". But depending on your definition of "hitting the feed" it sounds like we may be able to insert the CC into the actual email before it hits lore? That'd be very cool! At least for the lists already migrated from vger to korg?