public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
	Rebecca Cran <rebecca@bsdio.com>,
	 Liming Gao <gaoliming@byosoft.com.cn>,
	"Feng, Bob C" <bob.c.feng@intel.com>,
	 "Chen, Christine" <yuwei.chen@intel.com>,
	Michael Kubacki <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] [Patch 1/1] BaseTools/Scripts/PatchCheck: Error if commit modifies multiple packages
Date: Thu, 15 Feb 2024 00:47:46 +0100	[thread overview]
Message-ID: <CAMj1kXHXNz0w9HG6-CA+KLcs8rDn0eP9CWFKqpiRES5uSJx6=w@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB49299C467AF291435D40A966D24E2@CO1PR11MB4929.namprd11.prod.outlook.com>

On Thu, 15 Feb 2024 at 00:27, Michael D Kinney
<michael.d.kinney@intel.com> wrote:
>
> Hi Ard,
>
> Using commit message does provide granularity down to a single commit,
> which may be better than PR label which applies across all commits
> in a series.
>
> However, a flag in the commit message can be set by the author who may
> not be a maintainer and maintainers would then need to review commit
> messages for incorrect use of those flags.
>
> Only maintainers/admins can set labels, so from a permission management
> perspective the PR label has an advantage.
>
> Additional comments below.  There are ways to support bisect and meet
> the proposed checks. The suggestion uses techniques that Laszlo helped
> me with in the past when working on issues like there. I have seen more
> complex scenarios than the examples listed below, and have been able to
> figure out a path through.
>
> I would agree it is extra work to think about these when working on
> the code changes and extra work to reformulate the patches when these
> conditions are encountered.
>
> I just want to be clear on the objections.  It is not about if the patches
> can be organized to follow this proposal.  The objection is about the
> extra work required to reformulate patches.
>

No.

The objection is fundamentally about having to appease the CI even if
doing so is unreasonable. I don't mind a bit of extra work. I do mind
having to make code changes that make the code worse just to tick a CI
box. (This is why I disabled uncrustify for the ARM packages: many
header files which were perfectly legible before were converted into a
jumble of alphabet soup because uncrustify removed all of the
indentation)

It is about having the discretion to deviate from the rules in the odd
case where the cure is worse than the disease.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115473): https://edk2.groups.io/g/devel/message/115473
Mute This Topic: https://groups.io/mt/104345509/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-02-14 23:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  1:17 [edk2-devel] [Patch 1/1] BaseTools/Scripts/PatchCheck: Error if commit modifies multiple packages Michael D Kinney
2024-02-14  7:11 ` Ard Biesheuvel
2024-02-14 15:51   ` Michael D Kinney
2024-02-14 15:59     ` Ard Biesheuvel
2024-02-14 16:32       ` Leif Lindholm
2024-02-14 17:16         ` Michael D Kinney
2024-02-14 21:54           ` Ard Biesheuvel
2024-02-14 23:27             ` Michael D Kinney
2024-02-14 23:47               ` Ard Biesheuvel [this message]
2024-02-15  0:49                 ` Michael D Kinney
2024-02-18  3:36                   ` Michael D Kinney
2024-02-18  9:35                     ` Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMj1kXHXNz0w9HG6-CA+KLcs8rDn0eP9CWFKqpiRES5uSJx6=w@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox