public inbox for
 help / color / mirror / Atom feed
From: Jan Hubicka <>
Subject: GNU Tools Cauldron 2022
Date: Mon, 23 May 2022 12:22:29 +0200	[thread overview]
Message-ID: <> (raw)


We are pleased to invite you all to the next GNU Tools Cauldron,
taking place in Prague on September 16-18, 2022.  We are looking forward
to meet you again after three years!

As for the previous instances, we have setup a wiki page for
details:  <>

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 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  <>.

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.


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 10:22 Jan Hubicka [this message]
2022-09-16  7:49 ` Jan Hubicka

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).