From: Nick Clifton <nickc@redhat.com>
To: Paul Iannetta <piannetta@kalrayinc.com>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: [Binutils] Request for Write Access
Date: Tue, 23 Jan 2024 14:21:31 +0000 [thread overview]
Message-ID: <215bbf45-682f-46ce-9005-eb9271f0d33d@redhat.com> (raw)
In-Reply-To: <20240123132212.pd76qy3ywdvtn75n@ws2202.lin.mbt.kalray.eu>
Hi Paul,
[CC'ing the overseers....]
> 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.
> I already
> have an account on sourceware.org (for gcc), that is why I took the
> liberty of sending you a private e-mail, however if you think that it
> should have been a public email feel free to CC the binutils mailing
> list when replying.
No, a private request like this is fine.
> As before I'll submit all patches to the mailing-list for review
> before merging them in, and I'll wait for 2.42 to be out before
> merging patches.
Thanks.
> Would it be also possible to appear as the maintainer of the KVX port
> in the file binutils/MAINTAINERS?
Yes. In fact that would be the first thing I would ask you to do,
once you have write access. (Please also email the binutils list
saying that you are doing this).
Cheers
Nick
next parent reply other threads:[~2024-01-23 14:21 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 [this message]
2024-01-23 14:22 ` Frank Ch. Eigler
2024-01-23 15:24 ` Paul Iannetta
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=215bbf45-682f-46ce-9005-eb9271f0d33d@redhat.com \
--to=nickc@redhat.com \
--cc=overseers@sourceware.org \
--cc=piannetta@kalrayinc.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).