From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io, rebecca@bsdio.com, quic_rcran@quicinc.com
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Chris Fernald <chrisf671@gmail.com>
Subject: Re: [edk2-devel] [edk2-wiki][PATCH v1 0/4] Add new edk2 build instructions
Date: Mon, 5 Dec 2022 12:32:35 -0500 [thread overview]
Message-ID: <66e45804-b89e-4a9f-65d0-e34a1351dd3d@linux.microsoft.com> (raw)
In-Reply-To: <b9e49ba1-ff71-420d-ce10-0cbca3c8a8f8@bsdio.com>
I'm still trying to determine what to change for this particular series
to look correct on the mailing list.
In the meantime, if you want to see it, it is available here on my fork:
https://github.com/makubacki/tianocore.github.io/commits/add_stuart_build_instructions
Thanks,
Michael
On 12/5/2022 11:26 AM, Rebecca Cran wrote:
> 2/4 just came through.
>
> On 12/5/22 09:26, Michael Kubacki wrote:
>> Thanks, I'm working on it.
>>
>> On 12/5/2022 11:25 AM, Rebecca Cran wrote:
>>> Messages 1/4 and 4/4 are empty, and 2/4 seems to be missing.
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
next prev parent reply other threads:[~2022-12-05 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 16:15 [edk2-wiki][PATCH v1 0/4] Add new edk2 build instructions Michael Kubacki
2022-12-05 16:15 ` [edk2-wiki][PATCH v1 1/4] Add initial How to Build with Stuart Document Michael Kubacki
2022-12-05 16:15 ` [edk2-wiki][PATCH v1 2/4] Add initial container usage instructions Michael Kubacki
2022-12-05 16:15 ` [edk2-wiki][PATCH v1 3/4] Add top-level build instructions file Michael Kubacki
2022-12-05 16:15 ` [edk2-wiki][PATCH v1 4/4] Update existing build instructions Michael Kubacki
2022-12-05 16:25 ` [edk2-devel] [edk2-wiki][PATCH v1 0/4] Add new edk2 " Rebecca Cran
2022-12-05 16:26 ` Michael Kubacki
2022-12-05 16:26 ` Rebecca Cran
2022-12-05 17:32 ` Michael Kubacki [this message]
2022-12-05 17:42 ` Rebecca Cran
2022-12-05 19:46 ` 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=66e45804-b89e-4a9f-65d0-e34a1351dd3d@linux.microsoft.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