From: David Malcolm <dmalcolm@redhat.com>
To: Dodji Seketeli <dodji@seketeli.org>, Mark Wielaard <mark@klomp.org>
Cc: gcc@gcc.gnu.org, gdb@sourceware.org, binutils@sourceware.org,
libc-alpha@sourceware.org, "Jose E. Marchesi" <jemarch@gnu.org>,
Guinevere Larsen <blarsen@redhat.com>
Subject: Re: Anyone interesting to submit a GCC devroom request proposal at FOSDEM? (was Re: After Cauldron - online mini BoFs and Fosdem)
Date: Mon, 16 Oct 2023 14:31:53 -0400 [thread overview]
Message-ID: <728a78e16f5138e0c0a4b9c37446945dcadf8137.camel@redhat.com> (raw)
In-Reply-To: <87h6n7ubj0.fsf@seketeli.org>
On Tue, 2023-10-03 at 14:37 +0200, Dodji Seketeli wrote:
> Good day fine fellows!
>
> [...]
>
> Mark Wielaard <mark@klomp.org> a écrit:
>
> > Also Dodji, Jose and Gwen (on CC) are trying to coordinate a Fosdem
> > devroom for the various projects. Please contact them if you want
> > to
> > help out with that.
>
> So, José, Guinevere and myself have requested a "Binary Tools"
> devroom
> as well as a "Debugger and analysis tools" devroom for FOSDEM 2024.
>
> We still need two volunteers to submit a proposal for a "GCC &
> runtime
> libraries" devroom. The deadline for the devroom requests is 16
> October
> 2023: https://fosdem.org/2024/news/2023-09-29-devrooms-cfp.
>
> It would really be nice to have a GCC presence there.
>
I've used the form to request a "GCC devroom" for FOSDEM 2024.
If anyone wants to help out on the organizational side of this, it
would be most welcome!
Dave
next prev parent reply other threads:[~2023-10-16 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 15:46 After Cauldron - online mini BoFs and Fosdem Mark Wielaard
2023-10-03 12:37 ` Anyone interesting to submit a GCC devroom request proposal at FOSDEM? (was Re: After Cauldron - online mini BoFs and Fosdem) Dodji Seketeli
2023-10-16 18:31 ` David Malcolm [this message]
2023-10-17 14:24 ` 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=728a78e16f5138e0c0a4b9c37446945dcadf8137.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=binutils@sourceware.org \
--cc=blarsen@redhat.com \
--cc=dodji@seketeli.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jemarch@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.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).