From: "Wei Wu (吴伟)" <lazyparser@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: jiawei <jiawei@iscas.ac.cn>, gcc <gcc@gcc.gnu.org>,
"Christoph Muellner" <cmuellner@ventanamicro.com>,
libc-alpha@sourceware.org, gdb@sourceware.org,
sinan@isrc.iscas.ac.cn,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
"Nelson Chu" <nelson.chu@sifive.com>,
"Wei Wu (吴伟)" <wuwei2016@iscas.ac.cn>,
binutils@sourceware.org, "Kito Cheng" <kito.cheng@sifive.com>,
yulong@nj.iscas.ac.cn, shihua@iscas.ac.cn
Subject: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Aripl 07, 2022)
Date: Fri, 8 Apr 2022 12:54:11 +0800 [thread overview]
Message-ID: <CANkjrB6CJLVatb0ECcG5BimWWMVW8hgtPVwTnnegagwu3Of48w@mail.gmail.com> (raw)
In-Reply-To: <CANs6eM==y_YOr9OrQsLi7qyGN+knDr_0OevXMe1o4+HnyeAeVg@mail.gmail.com>
On Fri, Apr 8, 2022 at 12:23 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> I'm even more confused than normal here: I attempted to show up at 7am, as
> that's what my calendar said, ony to find that I couldn't get into Zoom and
> see a message from Eric saying the calendar here links to 8am but that the
> meeting was 7am. Then I saw Jim and Kito reply to my "sorry, Zoom is
> broken" message at 8am, saying the meeting was at 8am, so I went and had a
> meeting. After the meeting I talked to some folks who were in the 7am
> meeting, which evidently happened as well.
>
> Can we maybe get an auto-updated calendar for this meeting?
Oops. sorry for the confusion. There is an online version of ICS files
and Google Calendar.
The meeting time is bound to the UTC time zone, and the host may need
more attention during the daylight shifting month.
Online ICS File:
https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics
Google Calendar:
https://calendar.google.com/calendar/u/0?cid=bG01YmRkazJrcmNtdHY1aXB1dGpncXZvaW9AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
Embedded Link:
https://calendar.google.com/calendar/embed?src=lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com&ctz=Asia%2FIrkutsk
--
Best wishes,
Wei Wu (吴伟)
prev parent reply other threads:[~2022-04-08 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:11 jiawei
2022-04-07 9:20 ` Philipp Tomsich
[not found] ` <nk7d6utifco3uf8rvip44ih9.1649330207891@email.android.com>
2022-04-07 16:22 ` Palmer Dabbelt
2022-04-08 4:54 ` Wei Wu (吴伟) [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-all 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=CANkjrB6CJLVatb0ECcG5BimWWMVW8hgtPVwTnnegagwu3Of48w@mail.gmail.com \
--to=lazyparser@gmail.com \
--cc=binutils@sourceware.org \
--cc=cmuellner@ventanamicro.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=nelson.chu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=shihua@iscas.ac.cn \
--cc=sinan@isrc.iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
--cc=yulong@nj.iscas.ac.cn \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).