From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: libc-announce@sourceware.org, gdb@sourceware.org,
binutils@sourceware.org, cgen@sourceware.org, dejagnu@gnu.org,
newlib@sourceware.org, gcc@gcc.gnu.org
Subject: GNU Tools @ Linux Plumbers Conference 2021
Date: Wed, 23 Jun 2021 19:13:12 +0100 [thread overview]
Message-ID: <719e9cd5-6bca-cad0-f8ef-aa471b9e05e5@embecosm.com> (raw)
Hi all,
Once again we have been unable to hold GNU Tools Cauldron this year
due to COVID-19. We plan to be back in 2022!
In the meantime, our friends at the Linux Plumbers Conference have again
provided a GNU Tools track at their 2021 virtual conference 20-24 September.
The scope is the same as Cauldron, with talks, lightning talks,
tutorials and BoF sessions across all GNU tools: GlibC, GDB, binutils,
CGEN, DejaGnu, Newlib, GCC etc. We'll be using BigBlueButton as the
platform, and to try to fit in as many talks as possible, we'll be
restricting sessions to 25 minutes (10 minutes for lightning talks).
We invite your submissions. Full details at:
https://gcc.gnu.org/wiki/linuxplumbers2021
Note that we have a hard deadline of 31 August 2020. We are also using
the LPC submission system to keep things simple this year. Unlike
Cauldron, we won't be able to take late submissions, since we have to
tie in with the LPC 2021 infrastructure.
We look forward to seeing you (virtually) there. Any questions to
tools-cauldron-admin@googlegroups.com, discussion and future
announcements to gcc@gcc.gnu.org.
Best wishes,
Jeremy Bennett
on behalf of the organizing committee
(and apologies to those on multiple lists, who get this message
multiple times).
--
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
reply other threads:[~2021-06-23 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=719e9cd5-6bca-cad0-f8ef-aa471b9e05e5@embecosm.com \
--to=jeremy.bennett@embecosm.com \
--cc=binutils@sourceware.org \
--cc=cgen@sourceware.org \
--cc=dejagnu@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-announce@sourceware.org \
--cc=newlib@sourceware.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).