From: jiawei@iscas.ac.cn
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
libc-alpha@sourceware.org
Cc: christoph.muellner@vrull.eu, jeremy.bennett@embecosm.com,
jim.wilson.gcc@gmail.com, kito.cheng@sifive.com,
nelson.chu@sifive.com, palmer@dabbelt.com,
philipp.tomsich@vrull.eu, wuwei2016@iscas.ac.cn,
shihua@iscas.ac.cn, yulong@nj.iscas.ac.cn
Subject: [RISC-V] [SIG-toolchain] Meeting will be canceled (Agust 25, 2022)
Date: Wed, 24 Aug 2022 21:59:37 +0800 (GMT+08:00) [thread overview]
Message-ID: <621bab3.19df5.182d026c444.Coremail.jiawei@iscas.ac.cn> (raw)
Hi all,
Tommorrow's meeting will be canceled, since it during 2022 RISC-V Summit China .
The next RISC-V GNU toolchian meeting will be held on Sep 8.
Please let me know if you have any topics want to discuss in the next meeting.
Best Regards,
Jiawei
WARNING: multiple messages have this Message-ID
From: jiawei@iscas.ac.cn
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
libc-alpha@sourceware.org
Cc: christoph.muellner@vrull.eu, jeremy.bennett@embecosm.com,
jim.wilson.gcc@gmail.com, kito.cheng@sifive.com,
nelson.chu@sifive.com, palmer@dabbelt.com,
philipp.tomsich@vrull.eu, wuwei2016@iscas.ac.cn,
shihua@iscas.ac.cn, yulong@nj.iscas.ac.cn
Subject: [RISC-V] [SIG-toolchain] Meeting will be canceled (Agust 25, 2022)
Date: Wed, 24 Aug 2022 21:59:37 +0800 (GMT+08:00) [thread overview]
Message-ID: <621bab3.19df5.182d026c444.Coremail.jiawei@iscas.ac.cn> (raw)
Message-ID: <20220824135937.Ybpun430CAZOyMyDr6dDsrQnOAoMAbXF-Wo5noE_KnU@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
Hi all,
Tommorrow's meeting will be canceled, since it during 2022 RISC-V Summit China .
The next RISC-V GNU toolchian meeting will be held on Sep 8.
Please let me know if you have any topics want to discuss in the next meeting.
Best Regards,
Jiawei
next reply other threads:[~2022-08-24 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 13:59 jiawei [this message]
2022-08-24 13:59 ` jiawei
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=621bab3.19df5.182d026c444.Coremail.jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.com \
--cc=jim.wilson.gcc@gmail.com \
--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=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).