From: "Kubacki, Michael A" <michael.a.kubacki@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms/devel-MinPlatform] Specify this branch is read only after it is migrated to master
Date: Mon, 13 May 2019 18:59:56 +0000 [thread overview]
Message-ID: <49AB4ACB9627B8468F29D589A27B74558893A2B1@ORSMSX121.amr.corp.intel.com> (raw)
In-Reply-To: <20190513141612.19888-1-liming.gao@intel.com>
Since the branch is already moved to edk2-platforms/master, I immediately made
the update to redirect patch submissions to the master branch. This change is no
longer needed.
Thanks,
Michael
> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Liming Gao
> Sent: Monday, May 13, 2019 7:16 AM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] [edk2-platforms/devel-MinPlatform] Specify this
> branch is read only after it is migrated to master
>
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> ---
> ReadMe.md | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/ReadMe.md b/ReadMe.md
> index fbf735173f..f2dcee2e29 100644
> --- a/ReadMe.md
> +++ b/ReadMe.md
> @@ -1,3 +1,5 @@
> +# This branch has been migrated into master. Now, it is read only!
> +
> # **EDK II Minimum Platform Firmware for Intel(R) Platforms**
>
> The Minimum Platform is a software architecture that guides uniform
> delivery of Intel platforms enabling firmware
> --
> 2.13.0.windows.1
>
>
>
next prev parent reply other threads:[~2019-05-13 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 14:16 [edk2-platforms/devel-MinPlatform] Specify this branch is read only after it is migrated to master Liming Gao
2019-05-13 18:59 ` Kubacki, Michael A [this message]
2019-05-14 5:53 ` [edk2-devel] " Liming Gao
2019-05-15 0:37 ` Kubacki, Michael A
2019-05-15 0:44 ` 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=49AB4ACB9627B8468F29D589A27B74558893A2B1@ORSMSX121.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