From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Kubacki, Michael A" <michael.a.kubacki@intel.com>
Subject: Re: [Patch][edk2-platform] Migrate devel-MinPlatform branch to master branch
Date: Thu, 2 May 2019 15:35:14 +0100 [thread overview]
Message-ID: <20190502143514.2kw6ppapnilaxdmm@bivouac.eciton.net> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E430B25@SHSMSX104.ccr.corp.intel.com>
On Thu, Apr 25, 2019 at 01:08:33PM +0000, Gao, Liming wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1748
>
> There is no objection on the RFC https://edk2.groups.io/g/devel/topic/31236064#39516
> to migrate devel-MinPlatform branch to master branch.
Ah, I had completely missed that one due to not being on cc.
I do have a few comments, but I'll make those on the original email.
> This patch moves all patches in devel-MinPlatform branch to master branch.
> Here is the migrated code https://github.com/lgao4/edk2-platforms/tree/master_minplatform
> based on today history. All histories in devel-MinPlatform and master branches are kept.
> After this migration, the developer will check all the codes in edk2-platform master when
> he does the incompatible change in edk2 project. He doesn't need to check other branches.
This is certainly an improvement.
/
Leif
> When this patch submit, I will rebase master with the latest change
> in master and devel-MinPlatform.
>
> Signed-off-by: Liming Gao <liming.gao@intel.com<mailto:liming.gao@intel.com>>
next prev parent reply other threads:[~2019-05-02 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 13:08 [Patch][edk2-platform] Migrate devel-MinPlatform branch to master branch Liming Gao
2019-05-02 14:35 ` Leif Lindholm [this message]
2019-05-09 3:31 ` Liming Gao
2019-05-10 2:47 ` Kubacki, Michael A
2019-05-10 3:23 ` Liming Gao
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=20190502143514.2kw6ppapnilaxdmm@bivouac.eciton.net \
--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