From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: EDK II Development <edk2-devel@lists.01.org>,
"Gretzinger, Adam R" <adam.r.gretzinger@intel.com>,
Jeremiah Cox <jerecox@microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Chris Co <Christopher.Co@microsoft.com>,
Chad Mace <mimace@microsoft.com>,
Sean Brogan <sean.brogan@microsoft.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: Test message. Please ignore.
Date: Mon, 29 Oct 2018 18:31:47 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8B1D41D@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <DM5PR2101MB11284D86959960A09A3CFCB394F30@DM5PR2101MB1128.namprd21.prod.outlook.com>
Chris,
Thanks. That looks like what I expected.
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-
> bounces@lists.01.org] On Behalf Of Chris Co via edk2-
> devel
> Sent: Monday, October 29, 2018 11:22 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>;
> Gretzinger, Adam R <adam.r.gretzinger@intel.com>; edk2-
> devel@lists.01.org; Jeremiah Cox <jerecox@microsoft.com>
> Cc: Chris Co <Christopher.Co@microsoft.com>; Chad Mace
> <mimace@microsoft.com>; Sean Brogan
> <sean.brogan@microsoft.com>; Cetola, Stephano
> <stephano.cetola@intel.com>
> Subject: Re: [edk2] Test message. Please ignore.
>
> Hi Mike,
>
> Here is a Reply All to the test message.
>
> Chris
>
> > -----Original Message-----
> > From: Kinney, Michael D <michael.d.kinney@intel.com>
> > Sent: Monday, October 29, 2018 10:31 AM
> > To: Chris Co <Christopher.Co@microsoft.com>;
> Gretzinger, Adam R
> > <adam.r.gretzinger@intel.com>; edk2-
> devel@lists.01.org; Kinney, Michael D
> > <michael.d.kinney@intel.com>; Jeremiah Cox
> <jerecox@microsoft.com>
> > Cc: Sean Brogan <sean.brogan@microsoft.com>; Cetola,
> Stephano
> > <stephano.cetola@intel.com>; Chad Mace
> <mimace@microsoft.com>
> > Subject: RE: Test message. Please ignore.
> >
> > Hi Chris,
> >
> > This is a response to this test message. The Reply-To
> setting has been
> > updated to make sure edk2-devel is always present.
> >
> > Please do a Reply All to this test message.
> >
> > Thanks,
> >
> > Mike
> >
> > From: Chris Co [mailto:Christopher.Co@microsoft.com]
> > Sent: Friday, October 26, 2018 6:09 PM
> > To: Kinney, Michael D <michael.d.kinney@intel.com>;
> Gretzinger, Adam R
> > <adam.r.gretzinger@intel.com>; edk2-devel@lists.01.org
> > Cc: Sean Brogan <sean.brogan@microsoft.com>; Jeremiah
> Cox
> > <jerecox@microsoft.com>; Cetola, Stephano
> <stephano.cetola@intel.com>;
> > Chad Mace <mimace@microsoft.com>
> > Subject: Test message. Please ignore.
> >
> > Test message. Checking for DMARC bounces...
> >
> > Chris
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-10-29 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 1:09 Test message. Please ignore Chris Co
2018-10-29 17:31 ` Kinney, Michael D
2018-10-29 18:22 ` Chris Co
2018-10-29 18:31 ` Kinney, Michael D [this message]
2018-10-29 20:10 ` Kinney, Michael D
2018-10-29 20:11 ` Chris Co
2018-10-29 22:41 ` Kinney, Michael D
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=E92EE9817A31E24EB0585FDF735412F5B8B1D41D@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