From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"pedro.falcato@gmail.com" <pedro.falcato@gmail.com>,
Sean Brogan <spbrogan@outlook.com>
Cc: "Théo Jehl" <theojehl76@gmail.com>,
"Marvin Häuser" <mhaeuser@posteo.de>,
"Oram, Isaac W" <isaac.w.oram@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] edk2-platforms, continuous integration, testing, and you
Date: Mon, 16 Jan 2023 21:06:40 +0000 [thread overview]
Message-ID: <CO1PR11MB4929469744AEF5B5F20DC79FD2C19@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAKbZUD0LMGXWPJq4EWbea0hFBrzrP3N4DZsQxW+Z0mLU3Q+wGg@mail.gmail.com>
Hi Sean,
I moved this week's meeting to 10am pacific on Tuesday Jan 17th.
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Pedro Falcato
> Sent: Friday, January 13, 2023 6:54 PM
> To: Sean Brogan <spbrogan@outlook.com>
> Cc: Théo Jehl <theojehl76@gmail.com>; devel@edk2.groups.io; Marvin Häuser <mhaeuser@posteo.de>; Oram, Isaac W
> <isaac.w.oram@intel.com>
> Subject: Re: [edk2-devel] edk2-platforms, continuous integration, testing, and you
>
> On Fri, Jan 13, 2023 at 10:32 PM Sean Brogan <spbrogan@outlook.com> wrote:
> >
> > how about 10am pacific Jan 17th. should be 7pm your time?
> >
> > Thanks
> >
> > Sean
> >
> Hi Sean,
>
> Should work for me (6pm btw, GMT here).
>
> Thanks,
> Pedro
>
>
>
>
prev parent reply other threads:[~2023-01-16 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 21:38 edk2-platforms, continuous integration, testing, and you Sean
2023-01-04 23:57 ` [edk2-devel] " Pedro Falcato
2023-01-05 1:52 ` Sean
2023-01-05 23:32 ` Pedro Falcato
2023-01-05 23:48 ` Théo Jehl
2023-01-10 0:24 ` Isaac Oram
2023-01-13 22:32 ` Sean
2023-01-14 2:54 ` Pedro Falcato
2023-01-16 21:06 ` 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=CO1PR11MB4929469744AEF5B5F20DC79FD2C19@CO1PR11MB4929.namprd11.prod.outlook.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