public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gabriele SVELTO <gabriele.svelto@st.com>
To: overseers@sourceware.org
Cc: Erven Rohou <erven.rohou@st.com>
Subject: Re: Request from Gabriele Svelto
Date: Mon, 11 Feb 2008 17:25:00 -0000	[thread overview]
Message-ID: <47B01E65.3010302@st.com> (raw)
In-Reply-To: <20080208171320.GA2542@ednor.casa.cgf.cx>

Christopher Faylor wrote:
> On Thu, Feb 07, 2008 at 10:07:26AM -0000, gabriele.svelto@st.com wrote:
>> Gabriele Svelto 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=5017051.18220
> 
> As I understand the rules of the GCC project you need a well-known
> maintainer to sponsor write-after-approval privileges.
> 
> AFAICT (and I may well be missing something), your approver is only
> listed as having write-after-approval privileges.  He was approved for
> write-after-approval by Sebastian Pop who is listed as a maintainer.
> 
> So, I think we need some clarification here as to whether this is
> sanctioned by someone "important" in the gcc project.
> 
> cgf

Actually I think that I can get an approval by Sebastian Pop himself, however 
I'm unsure on what to do. Shall I just write to Sebastian Pop to get the 
approval or I have to refill the form for requesting a sourceware.org account 
for GCC? Thank you

  Gabriele Svelto

  reply	other threads:[~2008-02-11 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 16:59 gabriele.svelto
2008-02-10 19:10 ` Christopher Faylor
2008-02-11 17:25   ` Gabriele SVELTO [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-20 20:51 gabriele.svelto
2007-11-28 10:32 gabriele.svelto

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=47B01E65.3010302@st.com \
    --to=gabriele.svelto@st.com \
    --cc=erven.rohou@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).