From: Paul Iannetta <piannetta@kalrayinc.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: [Binutils] Request for Write Access
Date: Tue, 23 Jan 2024 15:24:02 +0000 [thread overview]
Message-ID: <MR1P264MB2482D94493162A2D8C8F058CA1742@MR1P264MB2482.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Za_LwiWCs8B9DghA@elastic.org>
From: Frank Ch. Eigler <fche@elastic.org>
Sent: 23 January 2024 15:22
To: Overseers mailing list <overseers@sourceware.org>
Cc: Paul Iannetta <piannetta@kalrayinc.com>; Nick Clifton <nickc@redhat.com>
Subject: Re: [Binutils] Request for Write Access
Hi -
> > Would you accept to sponsor me so that I can ask
> > admin-request@sourceware.org for write access for binutils.
>
> Certainly I would be happy to do so.
Done.
- FChE
Thank you, both
Paul
prev parent reply other threads:[~2024-01-23 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240123132212.pd76qy3ywdvtn75n@ws2202.lin.mbt.kalray.eu>
2024-01-23 14:21 ` Nick Clifton
2024-01-23 14:22 ` Frank Ch. Eigler
2024-01-23 15:24 ` Paul Iannetta [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=MR1P264MB2482D94493162A2D8C8F058CA1742@MR1P264MB2482.FRAP264.PROD.OUTLOOK.COM \
--to=piannetta@kalrayinc.com \
--cc=fche@elastic.org \
--cc=nickc@redhat.com \
--cc=overseers@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).