From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv To: Sean ,devel@edk2.groups.io From: "Sean" X-Originating-Location: Redmond, Washington, US (167.220.2.83) X-Originating-Platform: Windows Chrome 76 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 28 Jun 2019 15:13:33 -0700 References: <26138.1560319343440492230@groups.io> In-Reply-To: <26138.1560319343440492230@groups.io> Message-ID: <3011.1561760013073919526@groups.io> Content-Type: multipart/alternative; boundary="YEgfkyYve8noVVIgNqom" --YEgfkyYve8noVVIgNqom Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Wrapping up all comments on the RFC and requesting the RFC move to the impl= ementation phase. Changes after community discussion: * GitHub repository will be called edk2-pytool-extensions * 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 support= ed and it is best to create smaller individual pull requests. --YEgfkyYve8noVVIgNqom Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Wrapping up all comments on the RFC and requesting the RFC move to the impl= ementation 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 mak= e it clear that PRs will be squashed and therefore patch-sets are not suppo= rted and it is best to create smaller individual pull requests.  =

--YEgfkyYve8noVVIgNqom--