From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10992 invoked by alias); 11 Dec 2009 16:59:10 -0000 Received: (qmail 10985 invoked by uid 22791); 11 Dec 2009 16:59:08 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail3-relais-sop.national.inria.fr (HELO mail3-relais-sop.national.inria.fr) (192.134.164.104) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 11 Dec 2009 16:59:06 +0000 Received: from dingdong.irisa.fr (HELO [131.254.10.67]) ([131.254.10.67]) by mail3-relais-sop.national.inria.fr with ESMTP; 11 Dec 2009 17:59:02 +0100 Message-ID: <4B227A56.4060205@inria.fr> Date: Fri, 11 Dec 2009 16:59:00 -0000 From: Thierry LAFAGE User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4 MIME-Version: 1.0 To: overseers@sourceware.org Subject: Re: Account on sourceware.org for write access to gcc project References: <4B22731F.6070106@inria.fr> <20091211163421.GA27610@ednor.casa.cgf.cx> In-Reply-To: <20091211163421.GA27610@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00138.txt.bz2 Ok, thank you. BTW, in http://gcc.gnu.org/svnwrite.html, I did not see that I needed to get approval from a non-write-after-approval maintainer. I'll try and find one. Regards, Thierry Lafage. Le 11/12/2009 17:34, Christopher Faylor a écrit : > On Fri, Dec 11, 2009 at 05:28:15PM +0100, Thierry LAFAGE wrote: > >> Hi, >> >> In order to obtain write access to the GCC project on the CLI back-end >> branch (svn://gcc.gnu.org/svn/gcc/branches/st), I filled in the >> mentioned form (http://sourceware.org/cgi-bin/pdw/ps_form.cgi). Then >> Erven Rohou approved my request. >> Since then, I have no news, not even an acknowledgement e-mail for my >> request. >> So, I dare to post in this list to ask: is this normal? >> What should I do now? >> > Sorry. > > This fell through the cracks but, unfortunately, you have not followed > the right procedure to acquire write access. Even Rohou has > "write-after-approval" and does not have the authority to sponsor > anyone for write access to the gcc repository. > > You'll need to get approval from a non-write-after-approval maintainer. >