From: jiawei@iscas.ac.cn
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
libc-alpha@sourceware.org
Cc: cmuellner@ventanamicro.com, 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, sinan@isrc.iscas.ac.cn,
yulong@nj.iscas.ac.cn
Subject: [RISCV] RISC-V GNU Toolchain Meeting Cancell (Feb 09, 2022)
Date: Wed, 9 Feb 2022 19:42:44 +0800 (GMT+08:00) [thread overview]
Message-ID: <77a0c46a.11ec2.17ede4b02fe.Coremail.jiawei@iscas.ac.cn> (raw)
Hi all,
Tomorrow meeting will cancell due to there are few new topics to talk. If you have any topic want to talk in next meeting, please mail me and I will mark it into next meeting agenda.
Regrads,
PLCT Jiawei
next reply other threads:[~2022-02-09 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 11:42 jiawei [this message]
2022-03-23 14:02 jiawei
2022-04-20 16:13 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=77a0c46a.11ec2.17ede4b02fe.Coremail.jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=cmuellner@ventanamicro.com \
--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=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).