From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Date: Fri, 28 Jun 2019 22:22:12 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9D5A57D@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <3011.1561760013073919526@groups.io>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Hi Sean,
The edk2-pytool-extensions repo has been created.
Thanks,
Mike
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Sean via Groups.Io
Sent: Friday, June 28, 2019 3:14 PM
To: Sean <sean.brogan@microsoft.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Wrapping up all comments on the RFC and requesting the RFC move to the implementation phase.
Changes after community discussion:
1. GitHub repository will be called edk2-pytool-extensions
2. An additional comment will be added to the contribution process to make it clear that PRs will be squashed and therefore patch-sets are not supported and it is best to create smaller individual pull requests.
[-- Attachment #2: Type: text/html, Size: 40657 bytes --]
prev parent reply other threads:[~2019-06-28 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 2:55 RFC for Edk2-ToolEnv Sean
2019-05-14 4:01 ` [edk2-devel] " rebecca
2019-05-14 7:37 ` Sean
2019-05-14 22:24 ` rebecca
2019-05-14 23:23 ` Sean
2019-05-14 23:34 ` rebecca
2019-05-23 2:39 ` Michael D Kinney
2019-05-23 6:46 ` Sean
2019-05-23 17:14 ` Michael D Kinney
2019-06-11 18:55 ` Purma, Kondal R
2019-06-12 6:02 ` Sean
2019-06-28 22:13 ` Sean
2019-06-28 22:22 ` Michael D Kinney [this message]
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=E92EE9817A31E24EB0585FDF735412F5B9D5A57D@ORSMSX113.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