From: Olivier Hainque <hainque@adacore.com>
To: gcc@gcc.gnu.org, libc-announce@sourceware.org,
binutils@sourceware.org, cgen@sourceware.org, dejagnu@gnu.org,
gdb@sourceware.org, newlib@sourceware.org
Cc: Joel Brobecker <brobecke@adacore.com>,
Pamela Trevino <trevino@adacore.com>,
Juliana Silva <silva@adacore.com>
Subject: GNU Tools Cauldron 2020
Date: Thu, 23 Jan 2020 18:19:00 -0000 [thread overview]
Message-ID: <3FF841B4-BE1C-47D9-8B91-F6A63C28B9A4@adacore.com> (raw)
Hello,
We are pleased to invite you all to the next GNU Tools Cauldron,
taking place in Paris on June 12-14, 2020.
As for the previous instances, we have setup a wiki page for
details:
https://gcc.gnu.org/wiki/cauldron2020
The conference is free to attend, registration in advance is required.
To send abstracts or ask administrative questions, please email to
tools-cauldron-admin AT googlegroups.com.
To register, please fill out the following form:
https://forms.gle/4Tocg6JnTwqyJbwq8
If unable to use this form, please visit the Wiki page above for
alternative instructions on how to register.
The Cauldron is organized by a group of volunteers. We are keen to
add some more people so others can stand down. If you'd like to be
part of that organizing committee, please email the same address.
This announcement is being sent to the main mailing list of the
following groups: GCC, GDB, binutils, CGEN, DejaGnu, newlib and glibc.
Please feel free to share with other groups as appropriate.
Best Regards,
Olivier
next reply other threads:[~2020-01-23 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 18:19 Olivier Hainque [this message]
2020-01-23 19:02 ` Fadhili Juma
2020-01-23 19:12 ` Alfred M. Szmidt
2020-01-23 20:17 ` Florian Weimer
2020-01-23 21:18 ` Andrew Pinski
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=3FF841B4-BE1C-47D9-8B91-F6A63C28B9A4@adacore.com \
--to=hainque@adacore.com \
--cc=binutils@sourceware.org \
--cc=brobecke@adacore.com \
--cc=cgen@sourceware.org \
--cc=dejagnu@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-announce@sourceware.org \
--cc=newlib@sourceware.org \
--cc=silva@adacore.com \
--cc=trevino@adacore.com \
/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).