public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
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>
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: Re: Volunteer for release manager for glibc 2.38?
Date: Mon, 27 Mar 2023 12:08:28 -0400	[thread overview]
Message-ID: <e29430f6-fe4a-1df0-bb85-ec87057861c6@gotplt.org> (raw)
In-Reply-To: <5045722.vXUDI8C0e8@noumea>

On 2023-03-27 11:59, Andreas K. Huettel wrote:
> Am Montag, 27. März 2023, 16:47:21 CEST schrieb Siddhesh Poyarekar:
>>> As already discussed in private with Carlos and Adhemerval, I'd like to volunteer
>>> for 2.38 if there are no objections.
>>
>> You'll probably need write access for the repo then.
> 
> Aware of that, yes. :)
> 
> I have a sourceware account, but it's only approved for binutils so far.

Please make a request for glibc too, I'll be happy to approve.

Thanks,
Sid

  reply	other threads:[~2023-03-27 16:08 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 [this message]
2023-03-29 18:35       ` Carlos O'Donell

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=e29430f6-fe4a-1df0-bb85-ec87057861c6@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --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).