From: Andrew Pinski via Gdb <gdb@sourceware.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: gcc@gcc.gnu.org, gdb@sourceware.org, libc-alpha@sourceware.org,
binutils@sourceware.org
Subject: Re: Weekly news letter about GNU toolchain
Date: Thu, 4 Sep 2025 08:39:23 -0700 [thread overview]
Message-ID: <CALvbMcBBcNEo5EamZU_VOshQ3mCwUuu1Cs9Kbw_Ur+iRDdPMBA@mail.gmail.com> (raw)
In-Reply-To: <e3672f05-5bff-45e0-b50a-4f8ccf1fe16e@linaro.org>
On Thu, Sep 4, 2025 at 6:32 AM Adhemerval Zanella Netto
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 30/08/25 20:02, Andrew Pinski wrote:
> > To begin with it will be on mastodon:
> > https://hachyderm.io/@gnutoolsweekly
> >
> > But I might move it over to more blog like site instead of a social
> > media. Though was thinking about hosting on the wiki. I still have not
> > decided.
> >
> > I started a few weeks back on doing this on my personal mastodon
> > andlinkedin accounts but I decided to separate as the newsletter will
> > be more public.
> >
> > Thanks,
> > Andrew
>
> Thanks for working on this Andrew, this is great. Do you plan to cover only
> gcc or also related GNU toolchain projects? I can help you cover the glibc
> work.
I am planning on covering all GNU toolchain projects; including but
not limited to GCC, glibc, gdb, and binutils.
I will be adding glibc this week and then gdb the week after and
binutils in the week after that.
Thanks,
Andrew
prev parent reply other threads:[~2025-09-04 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 23:02 Andrew Pinski via Gdb
2025-09-03 22:24 ` Mark Wielaard
2025-09-03 22:34 ` Andrew Pinski via Gdb
2025-09-04 13:32 ` Adhemerval Zanella Netto via Gdb
2025-09-04 15:39 ` Andrew Pinski via Gdb [this message]
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=CALvbMcBBcNEo5EamZU_VOshQ3mCwUuu1Cs9Kbw_Ur+iRDdPMBA@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.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