From: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Organization of github.com/IntelFsp/FSP
Date: Wed, 11 Jul 2018 23:28:19 +0000 [thread overview]
Message-ID: <02A34F284D1DA44BB705E61F7180EF0AAE406E0A@ORSMSX114.amr.corp.intel.com> (raw)
Hi All,
Recently a discussion came up on the coreboot mailing list regarding the organization of the github.com/IntelFsp/FSP repository. Currently the repository is organized with each platform on its own branch. This organization makes it difficult to set up a git submodule that pulls the FSP, since "n" submodules will be needed where n == the number of platforms. An alternate organization would be to put all packages in to the master branch:
- ApolloLakeFspBinPkg
- BayTrailFspBinPkg
- BraswellFspBinPkg
- BroadwellFspBinPkg
- KabylakeFspBinPkg
- SkylakeFspBinPkg
- etc.
This would make it easier to configure a git submodule, and it would also more closely match the organization of github.com/tianocore/edk2. The idea seems reasonable to me. Does anyone here have thoughts or input?
With Best Regards,
Nate
reply other threads:[~2018-07-11 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=02A34F284D1DA44BB705E61F7180EF0AAE406E0A@ORSMSX114.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