From: "Jose E. Marchesi via Gdb" <gdb@sourceware.org>
To: GNU Tools weekly via Gcc <gcc@gcc.gnu.org>
Cc: binutils@sourceware.org, libc-alpha@sourceware.org,
gdb@sourceware.org, andrew.pinski@oss.qualcomm.com,
GNU Tools weekly <gnutoolsweekly@gmail.com>
Subject: Re: GNU Tools Weekly News Week 36 (May 3, 2026)
Date: Wed, 06 May 2026 10:38:50 +0200 [thread overview]
Message-ID: <87h5oldjad.fsf@gnu.org> (raw)
In-Reply-To: <CAHt=NyPX=1drCFkU_b7kCP_JmWYHtZAejKh4U1ia6j+MgmYEEQ@mail.gmail.com>
> GNU toolchain conference reminders:
> * FOSSY 2026 toolchain track North America, Aug 6-9 (Vancouver, Canada)
> * Call for Proposals: https://2026.fossy.ca/call-for-proposals/
> * GNU Tools Cauldron 2026, Fri-Sun, October 2-4 (Prague, Czechia)
> * https://gcc.gnu.org/wiki/cauldron2026
> * https://conf.gnu-tools-cauldron.org/prg26/cfp
This year LPC is also in Prague right after Cauldron, and we will be
doing a Toolchains track there. CFP is open.
* Toolchains Track at LPC 2026, October 7-7 (Prague, Czechia)
* https://lpc.events
next prev parent reply other threads:[~2026-05-06 10:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 5:44 GNU Tools Weekly News Week 2 (September 7, 2025) GNU Tools weekly via Gdb
2025-09-14 21:19 ` GNU Tools Weekly News Week 3 (September 14, 2025) GNU Tools weekly via Gdb
2025-09-22 3:43 ` GNU Tools Weekly News Week 4 (September 21, 2025) GNU Tools weekly via Gdb
[not found] ` <CAHt=NyNKa=eQ8ytymevK-r_Zz5p_DhzOzpYC35YLdqzJ4XhgMQ@mail.gmail.com>
2025-10-13 0:47 ` GNU Tools Weekly News Week 7 (October 12, 2025) GNU Tools weekly via Gdb
2025-10-20 7:58 ` GNU Tools Weekly News Week 8 (October 19, 2025) GNU Tools weekly via Gdb
2025-10-27 4:38 ` GNU Tools Weekly News Week 9 (October 26, 2025) GNU Tools weekly via Gdb
2025-11-03 7:50 ` GNU Tools Weekly News Week 10 (November 2, 2025) GNU Tools weekly via Gdb
2025-11-14 0:43 ` GNU Tools Weekly News Week 11 (November 9, 2025) GNU Tools weekly via Gdb
2025-11-14 0:51 ` GNU Tools weekly via Gdb
2025-11-17 7:00 ` GNU Tools Weekly News Week 12 (November 16, 2025) GNU Tools weekly via Gdb
2025-11-24 5:49 ` GNU Tools Weekly News Week 13 (November 23, 2025) GNU Tools weekly via Gdb
2025-12-01 6:45 ` GNU Tools Weekly News Week 14 (November 30, 2025) GNU Tools weekly via Gdb
2025-12-08 8:54 ` GNU Tools Weekly News Week 15 (December 7, 2025) GNU Tools weekly via Gdb
2025-12-15 7:32 ` GNU Tools Weekly News Week 16 (December 14, 2025) GNU Tools weekly via Gdb
2025-12-22 8:51 ` GNU Tools Weekly News Week 17 (December 21, 2025) GNU Tools weekly via Gdb
2025-12-28 19:51 ` GNU Tools Weekly News Week 18 (December 28, 2025) GNU Tools weekly via Gdb
2026-01-05 8:20 ` GNU Tools Weekly News Week 19 (January 5, 2026) GNU Tools weekly via Gdb
2026-01-12 8:42 ` GNU Tools Weekly News Week 20 (January 11, 2026) GNU Tools weekly via Gdb
2026-01-19 8:46 ` GNU Tools Weekly News Week 21 (January 18, 2026) GNU Tools weekly via Gdb
2026-01-26 7:21 ` GNU Tools Weekly News Week 22 (January 25, 2026) GNU Tools weekly via Gdb
2026-02-02 10:19 ` GNU Tools Weekly News Week 23 (February 1, 2026) GNU Tools weekly via Gdb
2026-02-09 8:16 ` GNU Tools Weekly News Week 24 (February 8, 2026) GNU Tools weekly via Gdb
2026-02-16 5:32 ` GNU Tools Weekly News Week 25 (February 15, 2026) GNU Tools weekly via Gdb
2026-02-23 6:43 ` GNU Tools Weekly News Week 26 (February 22, 2026) GNU Tools weekly via Gdb
2026-03-02 6:38 ` GNU Tools Weekly News Week 27 (March 1, 2026) GNU Tools weekly via Gdb
2026-03-09 7:51 ` GNU Tools Weekly News Week 28 (March 8, 2026) GNU Tools weekly via Gdb
2026-03-16 5:33 ` GNU Tools Weekly News Week 29 (March 15, 2026) GNU Tools weekly via Gdb
2026-03-23 19:40 ` GNU Tools Weekly News Week 30 (March 22, 2026) GNU Tools weekly via Gdb
2026-03-30 11:36 ` GNU Tools Weekly News Week 31 (March 29, 2026) GNU Tools weekly via Gdb
2026-04-06 8:57 ` GNU Tools Weekly News Week 32 (April 5, 2026) GNU Tools weekly via Gdb
2026-04-13 6:06 ` GNU Tools Weekly News Week 33 (April 12, 2026) GNU Tools weekly via Gdb
2026-04-20 5:10 ` GNU Tools Weekly News Week 34 (April 19, 2026) GNU Tools weekly via Gdb
2026-04-25 23:52 ` GNU Tools Weekly News Week 35 (April 26, 2026) GNU Tools weekly via Gdb
2026-04-25 23:59 ` GNU Tools weekly via Gdb
2026-05-04 1:34 ` GNU Tools Weekly News Week 36 (May 3, 2026) GNU Tools weekly via Gdb
2026-05-06 8:38 ` Jose E. Marchesi via Gdb [this message]
2026-05-11 6:15 ` GNU Tools Weekly News Week 37 (May 10, 2026) GNU Tools weekly via Gdb
2026-05-18 9:39 ` GNU Tools Weekly News Week 38 (May 17, 2026) GNU Tools weekly via Gdb
2026-05-25 5:47 ` GNU Tools Weekly News Week 39 (May 24, 2026) GNU Tools weekly via Gdb
2026-05-31 16:39 ` GNU Tools Weekly News Week 40 (May 31, 2026) GNU Tools weekly via Gdb
2026-06-08 20:56 ` GNU Tools Weekly News Week 41 (June 7, 2026) GNU Tools weekly via Gdb
2026-06-15 7:21 ` GNU Tools Weekly News Week 42 (June 14, 2026) GNU Tools weekly via Gdb
2026-06-22 5:21 ` GNU Tools Weekly News Week 43 (June 21, 2026) GNU Tools weekly via Gdb
2026-06-28 21:24 ` GNU Tools Weekly News Week 44 (June 28, 2026) GNU Tools weekly via Gdb
2026-07-05 7:19 ` GNU Tools Weekly News Week 45 (July 5, 2026) GNU Tools weekly via Gdb
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=87h5oldjad.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gnutoolsweekly@gmail.com \
--cc=jemarch@gnu.org \
--cc=libc-alpha@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