public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Dong Wei <Dong.Wei@arm.com>, "Jin, Eric" <eric.jin@intel.com>
Subject: Re: [RFC] Create new edk2-test repo
Date: Mon, 8 Oct 2018 00:30:01 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8AFD027@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <AM4PR08MB27882012FB67025A2B506E0B80EB0@AM4PR08MB2788.eurprd08.prod.outlook.com>

Supreeth,

I have created the edk2-test repository with the 
Readme.md, License.txt, and Contributions.txt files.

I have also created the "EDK II Test Maintainers"
team for developers that are maintainers of the test
infrastructure and test cases in this repository.

Best regards,

Mike

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-
> bounces@lists.01.org] On Behalf Of Supreeth Venkatesh
> Sent: Friday, October 5, 2018 9:53 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>;
> edk2-devel@lists.01.org
> Cc: Dong Wei <Dong.Wei@arm.com>; Jin, Eric
> <eric.jin@intel.com>
> Subject: Re: [edk2] [RFC] Create new edk2-test repo
> 
> Thanks Mike. I second that.
> Also, UEFI-SCT needs to find a place within edk2-test.
> Hope we can get this created before UEFI Taipei PlugFest
> (Oct 16) and after everyone's comments/review and
> approval.
> 
> Thanks,
> Supreeth
> 
> -----Original Message-----
> From: edk2-devel <edk2-devel-bounces@lists.01.org> On
> Behalf Of Kinney, Michael D
> Sent: Tuesday, September 25, 2018 6:34 PM
> To: edk2-devel@lists.01.org; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: [edk2] [RFC] Create new edk2-test repo
> 
> This is a proposal to create a new repository for tests
> called edk2-test.
> 
> The purpose of this repository is to provide test
> harnesses and test cases to test EDK II based firmware.
> 
> There is test related content in edk2-staging branches
> and as that content is completed, a location for tests
> is required.  This will provide core and platform
> developers the ability to test changes before commits
> are made and also provide a place to add new test cases
> for new features and functionality.
> 
> Thanks,
> 
> Mike
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> IMPORTANT NOTICE: The contents of this email and any
> attachments are confidential and may also be privileged.
> If you are not the intended recipient, please notify the
> sender immediately and do not disclose the contents to
> any other person, use it for any purpose, or store or
> copy the information in any medium. Thank you.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2018-10-08  0:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 23:33 [RFC] Create new edk2-test repo Kinney, Michael D
2018-10-05 16:53 ` Supreeth Venkatesh
2018-10-08  0:30   ` Kinney, Michael D [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=E92EE9817A31E24EB0585FDF735412F5B8AFD027@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