public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Jan Hubicka <hubicka@kam.mff.cuni.cz>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GNU Tools Cauldron 2022
Date: Sat, 14 May 2022 19:10:33 -0400	[thread overview]
Message-ID: <CAGWvnyn6vG-H31zgp5gxGSDeKOAxXzN+08av+Gi1ja0NnJayHg@mail.gmail.com> (raw)
In-Reply-To: <YoA0763ri5+sFneR@kam.mff.cuni.cz>

On Sat, May 14, 2022 at 7:03 PM Jan Hubicka via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hello,
>
> We are pleased to invite you all to the next GNU Tools Cauldron,
> taking place in Paris on September 16-18, 2022.  We are looking forward
> to meet you again after three years!

Did you intend to announce the location as Prague, Czechia, not Paris, France?

>
> As for the previous instances, we have setup a wiki page for
> details:
>
>      https://gcc.gnu.org/wiki/cauldron2022  <https://gcc.gnu.org/wiki/cauldron2022>
>
> In previous years we have been able to make the Cauldron free to all to attend
> thanks to the generosity of our sponsors. However this 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 £200.
>
> 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.
>
> We will also make it possible to attend remotely in the hybrid form and
> remote attendance will be for free as well.
>
> Please email to tools-cauldron-admin AT googlegroups.com if you would like to
> attend, indicating your T-shirt size and any dietary requirements. We'll
> contact you later in the year with details of how to pay.
>
> To send abstracts or ask administrative questions, please email to
> tools-cauldron-admin AT googlegroups.com  <http://googlegroups.com>.
>
> 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.
>
> Honza

  reply	other threads:[~2022-05-14 23:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 23:02 Jan Hubicka
2022-05-14 23:10 ` David Edelsohn [this message]
2022-05-14 23:14   ` Jan Hubicka
2022-09-02 19:44 ` Thomas Schwinge
2022-09-16  7:47 ` Jan Hubicka
2022-09-28 17:03   ` Vineet Gupta
2022-09-28 17:11     ` Vineet Gupta

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=CAGWvnyn6vG-H31zgp5gxGSDeKOAxXzN+08av+Gi1ja0NnJayHg@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@kam.mff.cuni.cz \
    /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).