From: Roberto COSTA <roberto.costa@st.com>
To: overseers@sourceware.org
Cc: Andrea BONA <andrea.bona@st.com>
Subject: Re: Request from Andrea Bona
Date: Wed, 15 Nov 2006 09:22:00 -0000 [thread overview]
Message-ID: <455ADBB2.5070006@st.com> (raw)
In-Reply-To: <20061115012718.GA25800@trixie.casa.cgf.cx>
Hello Christopher,
sorry for the incomplete request, I admit that the statement about whom
can approve write-after-approval access escaped to my eyes.
Anyway...
Andrea is actively working on the CLI back-end project
(http://gcc.gnu.org/projects/cli.html), which the steering committee
approved a few months ago and which I'm currently maintaining.
This project is at an early stage and there is no plan yet for
integration in GCC mainline, that's why there is no mention of it in
MAINTAINERS file.
I hope this is sufficient for this request, I don't see the point in
denying write access to someone working on an approved project for which
the other project developers have specifically got write-after-approval
status.
But if bureaucracy forbids... well, no problem, just tell me and I will
literally follow the policy to grant Andrea the status that allows him
working on the project.
Thanks!
Roberto
Christopher Faylor wrote:
> On Mon, Nov 13, 2006 at 04:23:50PM -0000, andrea.bona@st.com wrote:
>> Andrea Bona 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=8257945.5724
>
> I'm sorry, but my reading of the gcc policy page indicates that global
> or well-established maintainers are allowed to give write access. The
> GCC maintainers list shows Robert Costa as having only
> write-after-approval access to the list so I don't think he qualifies.
>
> I hate to be pedantic about this but I think you should probably
> get permission either from the gcc steering committee or from a
> <quote>well-established maintainer<unquote>.
>
> See: http://gcc.gnu.org/svnwrite.html#policies
>
> Apologies again for rejecting this request.
>
> cgf
next prev parent reply other threads:[~2006-11-15 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 16:23 andrea.bona
2006-11-15 1:27 ` Christopher Faylor
2006-11-15 1:29 ` Christopher Faylor
2006-11-15 9:22 ` Roberto COSTA [this message]
2006-11-15 12:01 ` Christopher Faylor
2006-11-15 13:35 andrea.bona
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=455ADBB2.5070006@st.com \
--to=roberto.costa@st.com \
--cc=andrea.bona@st.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).