From: Carlos O'Donell <carlos@redhat.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha <libc-alpha@sourceware.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Rajalakshmi Srinivasaraghavan <rajis@linux.vnet.ibm.com>,
DJ Delorie <dj@redhat.com>, Stefan Liebler <stli@linux.ibm.com>,
Sam James <sam@gentoo.org>,
Michael Hudson-Doyle <michael.hudson@canonical.com>,
Andreas Schwab <schwab@suse.de>
Subject: Re: Volunteer for release manager for glibc 2.38?
Date: Wed, 29 Mar 2023 14:35:01 -0400 [thread overview]
Message-ID: <17eb9d5a-81b0-0587-3d67-58e142a71b04@redhat.com> (raw)
In-Reply-To: <3999004.MLUfLXkozy@noumea>
On 3/25/23 15:55, Andreas K. Huettel wrote:
> Am Donnerstag, 23. März 2023, 14:37:05 CET schrieb Carlos O'Donell via Libc-alpha:
>>
>> I haven't had any further volunteers. You ran 2.33, but I'm happy to provide
>> support and coaching for all the documented steps! :-)
>>
>>
>
> As already discussed in private with Carlos and Adhemerval, I'd like to volunteer
> for 2.38 if there are no objections.
Andreas,
Thank you again for volunteering!
I am incredibly excited to have a new perspective on the process and to improve the steps.
--
Cheers,
Carlos.
prev parent reply other threads:[~2023-03-29 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:30 Carlos O'Donell
2023-03-02 16:49 ` Adhemerval Zanella Netto
2023-03-23 13:37 ` Carlos O'Donell
2023-03-25 19:55 ` Andreas K. Huettel
2023-03-27 14:47 ` Siddhesh Poyarekar
2023-03-27 15:59 ` Andreas K. Huettel
2023-03-27 16:08 ` Siddhesh Poyarekar
2023-03-29 18:35 ` Carlos O'Donell [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=17eb9d5a-81b0-0587-3d67-58e142a71b04@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=dilfridge@gentoo.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=michael.hudson@canonical.com \
--cc=rajis@linux.vnet.ibm.com \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
--cc=stli@linux.ibm.com \
--cc=szabolcs.nagy@arm.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).