From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, kondal.r.purma@intel.com
Subject: Re: [edk2-devel] EDK II Python development process specification -draft
Date: Tue, 10 Mar 2020 14:05:54 -0600 [thread overview]
Message-ID: <9694D3C5-0483-43F4-B4F9-E023274EE274@bsdio.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
I just noticed a typo on the page about python tools: the heading says Falke8 instead of Flake8.
—
Rebecca Cran
>> On Mar 6, 2020, at 5:27 PM, Purma, Kondal R <kondal.r.purma@intel.com> wrote:
>
> Hi,
>
> The draft specification for EDK II Python development process for presentation made earlier now available .
>
>
>
> Presentation thread :
>
>
>
> https://edk2.groups.io/g/announce/message/92
>
>
>
>
> Wiki Page link for specification document:
>
>
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Draft-Specification
>
>
>
>
>
> GitBook link for specification document:
>
> https://edk2-docs.gitbooks.io/edk-ii-python-development-process-speicfication
>
>
>
> PDF version can be downloaded from:
>
> https://legacy.gitbook.com/download/pdf/book/edk2-docs/edk-ii-python-development-process-speicfication
>
>
>
>
>
> Draft version available for 2 week review period and seeking for feedback.
>
>
>
> Thanks,
>
> Kondal.
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2550 bytes --]
next reply other threads:[~2020-03-10 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 20:05 Rebecca Cran [this message]
2020-03-11 16:52 ` [edk2-devel] EDK II Python development process specification -draft Purma, Kondal R
2020-03-14 19:07 ` Purma, Kondal R
2020-03-16 10:21 ` Bob Feng
2020-03-24 20:22 ` Purma, Kondal R
2020-03-25 21:23 ` Purma, Kondal R
-- strict thread matches above, loose matches on Subject: below --
2020-03-07 0:27 Purma, Kondal R
2020-03-07 21:35 ` [edk2-devel] " Sean
2020-03-07 23:26 ` Purma, Kondal R
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=9694D3C5-0483-43F4-B4F9-E023274EE274@bsdio.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