public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, mikuback@linux.microsoft.com
Cc: Andrew Fish <afish@apple.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	 Michael D Kinney <michael.d.kinney@intel.com>,
	Pierre Gondois <pierre.gondois@arm.com>,
	 Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Abner Chang <abner.chang@amd.com>,  Min Xu <min.m.xu@intel.com>,
	Zhiguang Liu <zhiguang.liu@intel.com>,
	 Tuan Phan <tphan@ventanamicro.com>, Yu Pu <yu.pu@intel.com>,
	Ray Ni <ray.ni@intel.com>
Subject: Re: [edk2-devel] Commits Spanning Packages
Date: Wed, 31 Jan 2024 20:41:12 +0000	[thread overview]
Message-ID: <CAKbZUD2v2DtUx26BCaKhBkbKpoNfPihNWEkN5KS527vqQczntA@mail.gmail.com> (raw)
In-Reply-To: <67b9f5d7-c338-473c-9322-d26022ef8f32@linux.microsoft.com>

On Wed, Jan 31, 2024 at 6:58 PM Michael Kubacki
<mikuback@linux.microsoft.com> wrote:
>
> Some commits have been spanning packages. For a monolithic upstream repo
> like edk2, this makes ingesting commits downstream more tedious if
> project requirements do not necessitate all packages to be maintained.
>
> Below are examples of commits spanning packages. Many of these are more
> problematic because "core" packages like MdePkg, MdeModule, SecurityPkg,
> UefiCpuPkg, etc. are involved. OvmfPkg and ArmVirtPkg seem to be a
> common pairing. To focus the examples below, I excluded commits with
> that pair.
>
> The request is to limit crossing package boundaries as much as possible
> and for maintainers to assess package impact when merging changes.

Personally I'm all for making downstreams' lives easier, but I don't
see how one could pull off many of the changes you linked, in 2+
commits, without breaking bisection.

Pulling off 103fa647d159e3d76be2634d2653c2d215dd0d46 would require you
to duplicate the struct, change a bunch of usages of the old struct to
the new struct, then change the old one back. This is hugely annoying
and complicated, and we should avoid this kind of rigamarole if
possible.

-- 
Pedro


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



  parent reply	other threads:[~2024-01-31 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 18:58 [edk2-devel] Commits Spanning Packages Michael Kubacki
2024-01-31 19:33 ` Michael D Kinney
2024-01-31 20:41 ` Pedro Falcato [this message]
2024-01-31 21:03   ` Michael Kubacki

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=CAKbZUD2v2DtUx26BCaKhBkbKpoNfPihNWEkN5KS527vqQczntA@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