public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gcc@gcc.gnu.org
Cc: David Edelsohn <dje.gcc@gmail.com>,
	Carlos O'Donell <carlos@redhat.com>,
	Jan Hubicka <honza.hubicka@gmail.com>
Subject: GNU Tools Cauldron 2024
Date: Mon, 4 Mar 2024 15:10:07 +0000	[thread overview]
Message-ID: <d61d287b-6703-414a-94fb-001c53db0c51@embecosm.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 535 bytes --]

Hi all,

We are starting to put together the plans for this year's Cauldron.  We 
have a suggested date of 13-15 September, the weekend before LPC.

We have not finalized a host for the meeting. If you wish to host, 
please let me, David Edelsohn, Carlos O'Donnell or Jan Hubicka know ASAP.

Thanks,


Jeremy
-- 
Cell: +44 7970 676050 (UK), +49 172 683 5745 (Germany)
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

             reply	other threads:[~2024-03-04 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 15:10 Jeremy Bennett [this message]
2024-03-06  3:57 ` Bradley M. Kuhn
2024-03-06 19:02   ` Eric Gallager
2024-03-06 20:47     ` Bradley M. Kuhn
2024-03-29 14:44       ` Mark Wielaard
2024-03-29 17:01         ` Submission Deadline 2024-04-18, GNU toolchain track at FOSSY in Portland, OR, USA (Conference date: 2024-08-01 to 2024-08-04) (was Re: GNU Tools Cauldron 2024) Bradley M. Kuhn
2024-05-09 15:48 GNU Tools Cauldron 2024 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:
  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=d61d287b-6703-414a-94fb-001c53db0c51@embecosm.com \
    --to=jeremy.bennett@embecosm.com \
    --cc=carlos@redhat.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=honza.hubicka@gmail.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).