From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <gopanho@gmail.com>
Subject: 回复: [edk2-devel] 回复: [edk2-devel] TianoCore Bug Triage - APAC / NAMO - Tue, 02/02/2021 6:30pm-7:30pm #cal-reminder
Date: Tue, 2 Feb 2021 23:28:39 +0800 [thread overview]
Message-ID: <007201d6f978$1b6f5080$524df180$@byosoft.com.cn> (raw)
In-Reply-To: <10266.1612259364380776253@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Niels:
Yes. Now, the meeting doesn’t start. You can join the meeting on its time slot.
Thanks
Liming
发件人: bounce+27952+71058+4905953+8761045@groups.io <bounce+27952+71058+4905953+8761045@groups.io> 代表 Niels Holm Olsen
发送时间: 2021年2月2日 17:49
收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io
主题: Re: [edk2-devel] 回复: [edk2-devel] TianoCore Bug Triage - APAC / NAMO - Tue, 02/02/2021 6:30pm-7:30pm #cal-reminder
Hi
Out of curiosity and to follow up on my bugreport 3186, I would like to know if it makes sense and is ok if I try to join the TianoCore Bug Triage tonight/early tomorrow.
I have taken the liberty of following the link to meetingsamer and it resulted in a download of a webex.exe. Running this and logging in with my name and email I were told the meeting hasn't started yet - which makes sense at this point of hour.
I have no experience in using this meeting-app but hope it works out ok. Please let me know if I need any further preparation to join.
Looking forward to listen in and maybe help explain my observations and concern regarding the potential bug if needed.
Niels Holm Olsen
[-- Attachment #2: Type: text/html, Size: 4641 bytes --]
prev parent reply other threads:[~2021-02-02 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 2:30 TianoCore Bug Triage - APAC / NAMO - Tue, 02/02/2021 6:30pm-7:30pm #cal-reminder devel@edk2.groups.io Calendar
2021-02-02 2:40 ` 回复: [edk2-devel] " gaoliming
2021-02-02 9:49 ` [edk2-devel] " Niels Holm Olsen
2021-02-02 15:28 ` gaoliming [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='007201d6f978$1b6f5080$524df180$@byosoft.com.cn' \
--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