From: Carlos O'Donell <codonell@redhat.com>
To: maskray@google.com, overseers@sourceware.org,
Stan Shebs <stanshebs@google.com>
Subject: Re: Request from Fangrui Song
Date: Sat, 01 Feb 2020 04:55:00 -0000 [thread overview]
Message-ID: <3ca8961b-e0a2-86c2-4182-d07996a1953d@redhat.com> (raw)
In-Reply-To: <20200125214217.GA15467@cgf.cx>
On 1/25/20 4:42 PM, Christopher Faylor wrote:
> On Fri, Jan 24, 2020 at 11:07:10PM -0000, maskray.google.com via overseers wrote:
>> Fangrui Song would like to be added to sourceware.org.
>>
>> For more information, check out:
>> http://sourceware.org/cgi-bin/pdw/queue.cgi
>>
>> Or, check the specific request here:
>> http://sourceware.org/cgi-bin/pdw/details.cgi?file=2263303.54129
>
> Sorry, but if I read the rules right at: https://sourceware.org/glibc/wiki/MAINTAINERS
> you need to be approved by a project steward for access and Stan is not,
> AFAICT, one of those.those.
Christopher, That is correct. Stewards approve write access.
Stan, Please feel free to reach out to me so I can resolve this issue for you. Likewise you can reach out to any other steward. We mostly want to make sure that everyone is following correct copyright protocol.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-02-01 4:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 23:07 maskray.google.com via overseers
2020-01-25 21:42 ` Christopher Faylor
2020-02-01 4:55 ` Carlos O'Donell [this message]
2020-06-05 20:56 ` Stan Shebs
2020-06-05 21:08 ` Fāng-ruì Sòng
2020-06-08 21:13 ` Carlos O'Donell
2020-06-08 21:31 ` Fangrui Song
2020-06-08 21:36 ` Carlos O'Donell
2020-06-08 21:44 ` Fangrui Song
2020-06-08 21:28 maskray
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=3ca8961b-e0a2-86c2-4182-d07996a1953d@redhat.com \
--to=codonell@redhat.com \
--cc=maskray@google.com \
--cc=overseers@sourceware.org \
--cc=stanshebs@google.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).