From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
"Bi, Dandan" <dandan.bi@intel.com>,
edk2-devel-groups-io <devel@edk2.groups.io>,
Julien Grall <julien.grall@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Andrew Fish <afish@apple.com>, "Ni, Ray" <ray.ni@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"Steele, Kelly" <kelly.steele@intel.com>,
"Sun, Zailiang" <zailiang.sun@intel.com>,
"Qian, Yi" <yi.qian@intel.com>
Subject: Re: [patch 0/7] Move BaseUefiTianoCustomDecompressLib from IntelFrameworkModulePkg to MdeModulePkg
Date: Wed, 24 Apr 2019 17:23:51 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9C9DA5B@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu8mqZJUHh5xO5QnzB1g4+hF6T9Y6O96zWHStakgowcNgQ@mail.gmail.com>
Ard,
Using edk2 and edk2-non-osi as submodules in the edk2-platforms
repo does have some advantages. Each branch in edk2-platforms
can decide which release/tag/sha is required from dependent repos.
This provides a platform focused view of the EDK II project.
If using a release/tag/sha for the dependent repos, the content
is effectively being used as read-only content like we do for
the OpenSSL submodule.
When using the combination of edk2-platforms/master, edk2/master,
and edk2-non-osi/master, if changes are made in submodules, then
there are some additional complexities that the developer needs
to be aware. But this is a workflow that is required to make
sure a change in edk2/master does not break any platforms in
edk2-platforms/master. I think easily discovering a build break
is higher priority.
Thanks,
Mike
> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> Sent: Wednesday, April 24, 2019 6:04 AM
> To: Gao, Liming <liming.gao@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>; Bi, Dandan
> <dandan.bi@intel.com>; edk2-devel-groups-io
> <devel@edk2.groups.io>; Julien Grall
> <julien.grall@arm.com>; Leif Lindholm
> <leif.lindholm@linaro.org>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Andrew Fish
> <afish@apple.com>; Ni, Ray <ray.ni@intel.com>; Wang, Jian
> J <jian.j.wang@intel.com>; Wu, Hao A
> <hao.a.wu@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Steele, Kelly
> <kelly.steele@intel.com>; Sun, Zailiang
> <zailiang.sun@intel.com>; Qian, Yi <yi.qian@intel.com>
> Subject: Re: [patch 0/7] Move
> BaseUefiTianoCustomDecompressLib from
> IntelFrameworkModulePkg to MdeModulePkg
>
> On Wed, 24 Apr 2019 at 15:02, Gao, Liming
> <liming.gao@intel.com> wrote:
> >
> > Ard:
> > I prefer to keep them as the separate repo. One dummy
> Git repo can be introduced to submodule edk2, edk2-
> platform, edk2-non-osi, and others. User can use this git
> repo to get everything.
> >
>
> That is not really my point.
>
> A git submodule allows you to store *in* the dependent
> repository
> which exact commit in the core repository you depend on.
> A dummy git
> repo does not work the same way.
>
> > > -----Original Message-----
> > > From: Ard Biesheuvel
> [mailto:ard.biesheuvel@linaro.org]
> > > Sent: Wednesday, April 24, 2019 8:48 PM
> > > To: Gao, Liming <liming.gao@intel.com>
> > > Cc: Laszlo Ersek <lersek@redhat.com>; Bi, Dandan
> <dandan.bi@intel.com>; edk2-devel-groups-io
> <devel@edk2.groups.io>; Julien Grall
> > > <julien.grall@arm.com>; Leif Lindholm
> <leif.lindholm@linaro.org>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Andrew Fish
> > > <afish@apple.com>; Ni, Ray <ray.ni@intel.com>; Wang,
> Jian J <jian.j.wang@intel.com>; Wu, Hao A
> <hao.a.wu@intel.com>; Kinney,
> > > Michael D <michael.d.kinney@intel.com>; Steele, Kelly
> <kelly.steele@intel.com>; Sun, Zailiang
> <zailiang.sun@intel.com>; Qian, Yi
> > > <yi.qian@intel.com>
> > > Subject: Re: [patch 0/7] Move
> BaseUefiTianoCustomDecompressLib from
> IntelFrameworkModulePkg to MdeModulePkg
> > >
> > > On Wed, 24 Apr 2019 at 14:46, Gao, Liming
> <liming.gao@intel.com> wrote:
> > > >
> > > >
> > > > So, we need to consider the combination of edk2
> master + edk2-platform master. When do the incompatible
> change in edk2 master, we
> > > need to update edk2-platform master together.
> > > >
> > >
> > > Yes, it is either that, or we separate them properly,
> by pulling core
> > > EDK2 into edk2-platforms as a git submodule. That
> way, we can update
> > > the upstream commit depended upon instead of assuming
> that we are
> > > always updated in lockstep.
prev parent reply other threads:[~2019-04-24 17:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 13:52 [patch 0/7] Move BaseUefiTianoCustomDecompressLib from IntelFrameworkModulePkg to MdeModulePkg dandan.bi
2019-04-04 13:52 ` [patch 1/7] ArmVirtPkg: Update UefiDecompressLib instance Dandan Bi
2019-04-04 14:57 ` Laszlo Ersek
2019-04-05 1:10 ` Dandan Bi
2019-04-04 13:52 ` [patch 2/7] BeagleBoardPkg: " Dandan Bi
2019-04-04 15:26 ` Ard Biesheuvel
2019-04-05 1:03 ` [edk2-devel] " Dandan Bi
2019-04-04 13:52 ` [patch 3/7] EmulatorPkg: " Dandan Bi
2019-04-04 13:52 ` [patch 4/7] MdeModulePkg: Move BaseUefiTianoCustomDecompressLib to Dandan Bi
2019-04-04 14:21 ` [edk2-devel] " Laszlo Ersek
2019-04-05 1:21 ` Dandan Bi
2019-04-04 21:14 ` felixp
2019-04-05 1:00 ` Dandan Bi
2019-04-04 13:52 ` [patch 5/7] Nt32Pkg: Update to use UefiDecompressLib in MdeModulePkg Dandan Bi
2019-04-04 21:21 ` [edk2-devel] " Felix Polyudov
2019-04-05 0:52 ` Dandan Bi
2019-04-04 13:52 ` [patch 6/7] Quark: " Dandan Bi
2019-04-04 13:52 ` [patch 7/7] Vlv2TbltDevicePkg: " Dandan Bi
2019-04-08 3:30 ` Qian, Yi
2019-04-23 16:26 ` [patch 0/7] Move BaseUefiTianoCustomDecompressLib from IntelFrameworkModulePkg to MdeModulePkg Ard Biesheuvel
2019-04-23 23:13 ` [edk2-devel] " Dandan Bi
2019-04-24 9:52 ` Laszlo Ersek
2019-04-24 12:46 ` Liming Gao
2019-04-24 12:48 ` Ard Biesheuvel
2019-04-24 13:02 ` Liming Gao
2019-04-24 13:03 ` Ard Biesheuvel
2019-04-24 17:23 ` Michael D Kinney [this message]
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=E92EE9817A31E24EB0585FDF735412F5B9C9DA5B@ORSMSX113.amr.corp.intel.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