From: Arthur Cohen <arthur.cohen@embecosm.com>
To: "gcc-rust@gcc.gnu.org" <gcc-rust@gcc.gnu.org>
Subject: June Community Call
Date: Mon, 5 Jun 2023 21:52:58 +0200 [thread overview]
Message-ID: <5925138a-6cc7-5e17-197a-04ca9bd6b96d@embecosm.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 328 bytes --]
Hi everyone!
We'll be having our Monthly Community call on the 12th of June at 9am UTC.
link: https://meet.jit.si/gccrs-community-call-june
agenda: https://hackmd.io/@Rust-GCC/ry2ShhsLn
Let me know if you'd like to join and there are schedule conflicts - the
call can probably be moved around.
Kindly,
Arthur
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
reply other threads:[~2023-06-05 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5925138a-6cc7-5e17-197a-04ca9bd6b96d@embecosm.com \
--to=arthur.cohen@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
/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).