From: Richard Earnshaw <Richard.Earnshaw@arm.com>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GNU Tools Cauldron 2023
Date: Tue, 25 Jul 2023 18:01:25 +0100 [thread overview]
Message-ID: <a3740aa5-28a2-ce4a-8de8-b5151aa4865e@arm.com> (raw)
In-Reply-To: <3da0d957-d38b-5a8e-9d6a-f96ee9c2c368@arm.com>
It is now just under 2 months until the GNU Tools Cauldron.
Registration is still open, but we would really appreciate it if you
could register as soon as possible so that we have a clear idea of the
numbers.
Richard.
On 05/06/2023 14:59, Richard Earnshaw wrote:
> We are pleased to invite you all to the next GNU Tools Cauldron,
> taking place in Cambridge, UK, on September 22-24, 2023.
>
> As for the previous instances, we have setup a wiki page for
> details:
>
> https://gcc.gnu.org/wiki/cauldron2023
> <https://gcc.gnu.org/wiki/cauldron2023>
>
>
> Like last year, we are having to charge for attendance. We are still
> working out what we will need to charge, but it will be no more than £250.
>
> Attendance will remain free for community volunteers and others who do
> not have a commercial backer and we will be providing a small number of
> travel bursaries for students to attend.
>
> For all details of how to register, and how to submit a proposal for a
> track session, please see the wiki page.
>
> 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.
>
> Richard (on behalf of the GNU Tools Cauldron organizing committee).
next prev parent reply other threads:[~2023-07-25 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 13:59 Richard Earnshaw
2023-07-25 17:01 ` Richard Earnshaw [this message]
2023-08-07 15:40 ` Richard Earnshaw (lists)
2023-09-05 8:10 ` Thomas Schwinge
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=a3740aa5-28a2-ce4a-8de8-b5151aa4865e@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc@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).