From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id 80575AC1085 for ; Tue, 20 Feb 2024 14:48:54 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=rwq/y70PZBf7fLI2+edj0eLjltcFbZ11CfDaNcGDBdw=; c=relaxed/simple; d=groups.io; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject:To:Cc:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type; s=20140610; t=1708440533; v=1; b=jk0zOehR6NbIGUWZc3tt3qyXViFhKWsoeHXzZg2S7d6W2a8ZclC0S0O2Z+/dWIZ6nOg/oKbK vq32onduKZMOVb5gv0lVT/nVimkXqKp+gq2TyIzMmrdqA0jo/uAkl7hdTm0ewjgpdaO2u+v9Vas SDxlOMxPItBIEoSAhwgpo+Ow= X-Received: by 127.0.0.2 with SMTP id rpVcYY7687511xKd2DJUYoO3; Tue, 20 Feb 2024 06:48:53 -0800 X-Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mx.groups.io with SMTP id smtpd.web10.14717.1708440532549434498 for ; Tue, 20 Feb 2024 06:48:52 -0800 X-Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 0B87361189 for ; Tue, 20 Feb 2024 14:48:52 +0000 (UTC) X-Received: by smtp.kernel.org (Postfix) with ESMTPSA id B8784C43394 for ; Tue, 20 Feb 2024 14:48:51 +0000 (UTC) X-Received: by mail-lf1-f49.google.com with SMTP id 2adb3069b0e04-512be6fda52so1988440e87.0 for ; Tue, 20 Feb 2024 06:48:51 -0800 (PST) X-Gm-Message-State: pGgHEzZv9XvRcjEuytQmRpAmx7686176AA= X-Google-Smtp-Source: AGHT+IENf3ClCq814IKy7K2RmTn8N1Xs6M48/cvQR1A6vMRTwiNh0W+ZcYlHDMEHk5aVRVtDXO7X9QpZUdZtIfi0haI= X-Received: by 2002:a05:6512:159:b0:512:a93a:f5a1 with SMTP id m25-20020a056512015900b00512a93af5a1mr4869267lfo.36.1708440529749; Tue, 20 Feb 2024 06:48:49 -0800 (PST) MIME-Version: 1.0 References: <20240218205951.497-1-michael.d.kinney@intel.com> <20240218205951.497-4-michael.d.kinney@intel.com> In-Reply-To: <20240218205951.497-4-michael.d.kinney@intel.com> From: "Ard Biesheuvel" Date: Tue, 20 Feb 2024 15:48:36 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [edk2-devel] [Patch 3/4] BaseTools/Scripts/PatchCheck: Error if no Cc tags are present To: devel@edk2.groups.io, michael.d.kinney@intel.com Cc: Rebecca Cran , Liming Gao , Bob Feng , Yuwei Chen , Michael Kubacki Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,ardb@kernel.org List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: Content-Type: text/plain; charset="UTF-8" X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=jk0zOehR; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=kernel.org (policy=none); spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io Hello Mike, I understand the desire to be pedantic about cc'ing the right maintainers, but I'm not convinced this is the way. - the presence of a cc: tag does not guarantee that the person was cc'ed - only git send-email will take CC:s in the message body into account by default (but this can also be disabled), but generally, the sender has to ensure the cc list is copied into the cc: field - the absence of a cc: tag does not imply that the person was not cc'ed, - in Linux, the cc: tag has slightly different semantics from the ones we appear to be assuming here: a cc tag in patch going into the repository is a statement by the maintainer that the person in question has been cc'ed, may have some 'jurisdiction' over the area, but hasn't bothered to respond. IOW, it is to record the fact that this person has been given the opportunity to respond. Then there is the matter of a maintainer that has reviewed the patch themselves. I usually remove the cc lines listing people that have reviewed/acked/tested the patch, as those tags already convey that the person is aware of it cc'ed or not. So perhaps it would be better to make this check part of the contributor workflow but not the GitHub PR/CI workflow? On Sun, 18 Feb 2024 at 22:00, Michael D Kinney wrote: > > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4694 > > If no Cc tags are detected in a commit message, then generate an > error. All patches sent for review are required to provide the set > of maintainers and reviewers responsible for the directories/files > modified. The set of maintainers and reviewers are documented in > Maintainers.txt and can be retrieved using the script > BaseTools/Scripts/GetMaintainer.py. > > Cc: Rebecca Cran > Cc: Liming Gao > Cc: Bob Feng > Cc: Yuwei Chen > Cc: Michael Kubacki > Signed-off-by: Michael D Kinney > --- > BaseTools/Scripts/PatchCheck.py | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/BaseTools/Scripts/PatchCheck.py b/BaseTools/Scripts/PatchCheck.py > index 158a2b30a5ce..415198e3824e 100755 > --- a/BaseTools/Scripts/PatchCheck.py > +++ b/BaseTools/Scripts/PatchCheck.py > @@ -229,8 +229,10 @@ class CommitMessageCheck: > ) > > def check_misc_signatures(self): > - for sig in self.sig_types: > - self.find_signatures(sig) > + for sigtype in self.sig_types: > + sigs = self.find_signatures(sigtype) > + if sigtype == 'Cc' and len(sigs) == 0: > + self.error('No Cc: tags for maintainers/reviewers found!') > > cve_re = re.compile('CVE-[0-9]{4}-[0-9]{5}[^0-9]') > > -- > 2.40.1.windows.1 > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#115653): https://edk2.groups.io/g/devel/message/115653 Mute This Topic: https://groups.io/mt/104434584/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-