From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19992 invoked by alias); 19 May 2006 13:03:41 -0000 Received: (qmail 19984 invoked by uid 22791); 19 May 2006 13:03:40 -0000 X-Spam-Check-By: sourceware.org Received: from intranet.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.6) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 19 May 2006 13:03:37 +0000 Received: (qmail 3643 invoked from network); 19 May 2006 13:03:35 -0000 Received: from unknown (HELO ?10.0.0.101?) (shinwell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 19 May 2006 13:03:35 -0000 Message-ID: <446DC21F.5050508@codesourcery.com> Date: Fri, 19 May 2006 15:37:00 -0000 From: Mark Shinwell User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Gerald Pfeifer CC: Paul Brook , gcc-patches@gcc.gnu.org, Mike Stump Subject: Re: Add myself to MAINTAINERS References: <446C5FE9.30500@codesourcery.com> <6A6957D5-4F1C-46B0-B4F4-DB802B4E899B@apple.com> <200605181820.06141.paul@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2006-05/txt/msg00982.txt.bz2 Gerald Pfeifer wrote: >> Admittedly "following instructions below" is somewhat vague, but I was >> under the impression that anyone with write-after-approval access should >> automatically add themselves to the MAINTAINERS file. > > Should as in RFC lingo, yes. Do you have a proposal on how to improve > wording of this page, Paul (or Mark)? We want our documentation to be > as clear as possible. How about: "Once we have this information we will set up an account on gcc.gnu.org and inform you by mail. At this point you should check out a tree with SVN using the instructions below and add yourself to the MAINTAINERS file. Having done this, you should produce a diff to this file and circulate it to the gcc-patches list, whilst also checking in your change to test write access. For all other changes, please be sure to follow the write access policies below." Mark