From: "Kevin@Insyde" <kevin.davis@insyde.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Guptha, Soumya K" <soumya.k.guptha@intel.com>,
"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>
Subject: Re: Extend TianoCore Bug Triage - APAC / NAMO Meeting from 0.5 hour to 1 hour
Date: Thu, 12 Mar 2020 13:58:47 -0500 [thread overview]
Message-ID: <1CBAF5E7-64CC-44CA-9EFC-B700BF2AD42D@insyde.com> (raw)
In-Reply-To: <551589efdd9641299b63825f1b5d3d95@intel.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
That conflicts for me for the first 30 minutes
Kevin D Davis
Security Strategist
Insyde Software
Phone: 503-310-2222
> On Mar 12, 2020, at 9:29 AM, Gao, Liming <liming.gao@intel.com> wrote:
>
>
> Hi, all
> Recently, regular TianoCore Bug Triage meeting has no enough time to review and discuss the existing bugzillas. I would propose to extend this meeting from 0.5 hour to 1 hour. Now, Bug Triage, Tiano Design and Community meeting are all in one day. I have met some conflict to those meeting. Some people may also have the conflict. So, I suggest to move TianoCore Bug Triage - APAC / NAMO Meeting to Wednesday morning 9:00AM ~ 10:00AM (UTC +8). If you have comments, please reply this mail. If no more comments, I will set up the first meeting from next week.
>
> Thanks
> Liming
[-- Attachment #2: Type: text/html, Size: 3982 bytes --]
next prev parent reply other threads:[~2020-03-12 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 14:28 Extend TianoCore Bug Triage - APAC / NAMO Meeting from 0.5 hour to 1 hour Liming Gao
2020-03-12 18:58 ` Kevin@Insyde [this message]
2020-03-16 13:51 ` [edk2-devel] " Liming Gao
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=1CBAF5E7-64CC-44CA-9EFC-B700BF2AD42D@insyde.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