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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3780BC6FA8F for ; Wed, 30 Aug 2023 07:11:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=5ETdc0SXo2hOWU98gEaCF0flow1tuB+gDbIPLtdnsVI=; b=1WIQRlN578PBTp QiZEkKvKGLv+rLtDD+pix7EtzGFDtbFm8VF2ffFhZ4GoYRmoVjwcVc+1Kc5u6dxwwkxRo3Y0iEBEA WvErMy6+FwGgLRUvm7lIwQTugNaKppTIsVwVBoppLz47aJ1ALsriHz6wX0BwxJ9jNUv72mOa9yEdx k2wPy65BVpMmvQb1kWJUPENLdKPlHMXXFUexKBz0O0JagdIEE8GRUmTBOPb3Lqr76TrpMh86w5uRN gfhD+m4B9S+Zy5mUPr27p5NqaUMSbtwP4GItCbI+UUOhEP4vfdb/7IemeBS34EJhCo9yCV5zoTAWM 3yj+2x0oVIn+au2AjPHQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qbFMP-00CyHB-0m; Wed, 30 Aug 2023 07:11:29 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qbFMM-00CyGE-25 for linux-arm-kernel@lists.infradead.org; Wed, 30 Aug 2023 07:11:28 +0000 Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5280ef23593so6817814a12.3 for ; Wed, 30 Aug 2023 00:11:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1693379482; x=1693984282; darn=lists.infradead.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=4X810Sd+FAfinOuDeQjJFxdDeSuw3tPSc7gW/bUxxmc=; b=f0nPsUXcbF8fRSUNNe+PWSyQ7am7A2skfhrqJ1X3WE6I4MhXDLtE+xsn/kn/bd70Cg 6mcFhNQzn43v/49fd9Th/BpoTZ8TNwUOze/7FJrvjSH2eB7MOaSaAqE/yws0nEBfI0d+ 4/3weMeF8TguNvP5dBbs5++boG1szrtj95pdTYiU7cd9uZG/SUeapWx+1RNupFb5gouH 9cRa6U2fhY6Puqf4Ctki8CIMOW0PVWXIFlbG1c3ibNyVGQHUnK4OD7ItwHeZoYO0SEy/ Qq9PaMuT7HcH3WUuLnGmcd7y3NjbU5Iby0oiAntorIioGUoGo4Il6b0R/6xvn1+cKWKy 4Ung== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693379482; x=1693984282; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4X810Sd+FAfinOuDeQjJFxdDeSuw3tPSc7gW/bUxxmc=; b=T8bgl3L8vljjgP4cAepcKKmd6sl8iWqBZqFKANZj8DJDrX7zoY9sBdNO6OCiBxoXRL bRVtPW6X+lKsDlWYxkRdtd1kYzdp8yLj9rJeXgc24FyL+gk0TnJ7fXbeUyF8m3lGttDq 5hnP3PsZMgSKVDF5As4GEPbvQAODNec7n6y8CuhMwgToSwTNKqkJnOdsr9I2pqqByGoZ vaCjNT1W5ZkPiffnPA0zOX8BJRV8XV2zzy/puZes0wvTi3fL4IQMZQ4AOpU/zaOt4AIV w0RAr/i/kTw5bIJgSzPIpvmg9dx0OEeEr56bUeerbcAv5C51ryJs9BcRQeHIgd56GJNO Wz+w== X-Gm-Message-State: AOJu0YwCUNmxmpNjjPZksDb+QzoRjkNHczJ9kWqQke+SD8nvkMzCjASA zaUJokGTuV7oJO/yihOzWsodxA== X-Google-Smtp-Source: AGHT+IEYCPnvQKeOC3qIczHiEZucOO/GNEh252whblJjg9K7h3SNi2mOr9jig7a/o2KtxMadPr1MLQ== X-Received: by 2002:a17:906:76c8:b0:9a1:d67c:b4eb with SMTP id q8-20020a17090676c800b009a1d67cb4ebmr913139ejn.48.1693379482411; Wed, 30 Aug 2023 00:11:22 -0700 (PDT) Received: from [192.168.0.22] (77-252-46-238.static.ip.netia.com.pl. [77.252.46.238]) by smtp.gmail.com with ESMTPSA id n11-20020a17090625cb00b009934855d8f1sm6910043ejb.34.2023.08.30.00.11.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Aug 2023 00:11:21 -0700 (PDT) Message-ID: Date: Wed, 30 Aug 2023 09:11:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: [PATCH v3 1/1] scripts: Add add-maintainer.py Content-Language: en-US To: Mark Brown , Masahiro Yamada , Nick Desaulniers , Andrew Morton , Nicolas Schier , Konstantin Ryabitsev , Kees Cook , Bjorn Andersson , robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, Will Deacon , Greg Kroah-Hartman , quic_pkondeti@quicinc.com, linux-kernel@vger.kernel.org, kernel@quicinc.com, workflows@vger.kernel.org, tools@linux.kernel.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org References: <141b9fcab2208ace3001df4fc10e3dfd42b9f5d9.1693037031.git.quic_gurus@quicinc.com> <2efba6b3-2399-9deb-d0ce-78f7b5e12f30@linaro.org> <20230828175629.GC23466@quicinc.com> <78aa33f9-ead8-b128-2a7a-40530a1a3ed0@linaro.org> <670a87e9-2f0c-ec9e-ebb4-9041c8972ace@linaro.org> <20230829231638.GA27843@quicinc.com> From: Krzysztof Kozlowski In-Reply-To: <20230829231638.GA27843@quicinc.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230830_001126_692215_E88D0FE5 X-CRM114-Status: GOOD ( 30.51 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 30/08/2023 01:16, Guru Das Srinagesh wrote: > On Aug 28 2023 21:45, Krzysztof Kozlowski wrote: >> On 28/08/2023 21:41, Mark Brown wrote: >>> On Mon, Aug 28, 2023 at 07:59:54PM +0200, Krzysztof Kozlowski wrote: >>>> On 28/08/2023 19:56, Guru Das Srinagesh wrote: >>> >>>>> Your function adds mailing lists also in "To:" which is not ideal, in my view. >>>>> You've mentioned before that To or Cc doesn't matter [1] which I disagree >>>>> with: it doesn't matter, why does Cc exist as a concept at all? >>> >>>> To/Cc does not matter when sending new patch, because maintainers know >>>> they are maintainers of which parts. I know what I handle. >>> >>> That might be true for you (and also is for me) but I know there are >>> people who pay attention to if they're in the To: for various reasons, I >>> gather it's mostly about triaging their emails and is especially likely >>> in cases where trees have overlaps in the code they cover. >> >> True, there can be cases where people pay attention to addresses of >> emails. Just like there are cases where people pay attention to "To/Cc" >> difference. >> >> In my short experience with a few patches sent, no one complained to me >> that I put him/her/they in "To" field of a patch instead of "Cc" (with >> remark to not spamming to much, so imagine I send a patch for regulator >> and DTS). Big, multi-subsystem patchsets are different case and this >> script does not solve it either. > > Not sure what you mean by "does not solve it" - what is the problem being > referred to here? Exactly, no one even knows what problem you want to solve by swapping To-Cc between patches... > > In case of multi-subsystem patches in a series, the commit message of this > patch explains exactly the actions taken. > >> Anyway, if it is not ideal for Guru, I wonder how his LKML maintainer >> filters work that it is not ideal? What is exactly not ideal in >> maintainer workflow? > > I am not a maintainer - only an individual contributor - and as such, even > though I may get patches on files I've contributed to, I deeply appreciate the > distinction between being Cc-ed in a patch vs To-ed in one. The distinction > being that if I'm in "To:" I ascribe higher priority to it and lesser if I'm in > "Cc:". That's your feeling, quite subjective. I understand it comes from corporate world, but again... > > If this script is accepted and gains adoption, maintainers like yourself will > only be To-ed in patches that touch files that you're a direct "Maintainer" or > "Reviewer" of. It will not get traction because: 1. People should use b4, not this script. 2. Remaining people will just use get_maintainers.pl. 3. People cannot get right even basic commands, so we will never be able to rely on To or Cc distinction. I can give you example: my email address in get_maintainers.pl is a bit different. Does it matter? Often not. Entire bunch of folks were Ccing me on different address. Even though every tool told them not to... > For all other patches in the series you'll be in "Cc:". I > imagine that this can be very useful regardless of the specifics of your > workflow. Zero usefulness for me. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel