From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7813 invoked by alias); 24 May 2006 08:31:41 -0000 Received: (qmail 7801 invoked by uid 22791); 24 May 2006 08:31:39 -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; Wed, 24 May 2006 08:31:29 +0000 Received: (qmail 16086 invoked from network); 24 May 2006 08:31:27 -0000 Received: from unknown (HELO ?10.0.0.101?) (shinwell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 24 May 2006 08:31:27 -0000 Message-ID: <447419D8.7020508@codesourcery.com> Date: Wed, 24 May 2006 12:38:00 -0000 From: Mark Shinwell User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Gerald Pfeifer CC: gcc-patches@gcc.gnu.org Subject: Re: Add myself to MAINTAINERS References: <446C5FE9.30500@codesourcery.com> <6A6957D5-4F1C-46B0-B4F4-DB802B4E899B@apple.com> <200605181820.06141.paul@codesourcery.com> <446DC21F.5050508@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/msg01232.txt.bz2 Gerald Pfeifer wrote: >> "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." > > I like this. > > I'd prefer to omit "with SVN" (which will make the migration easier in > case we switch version control systems at some point in the future) and > would omit the two occurrences of "you should", but these are only two > minor nits. Thanks for the patch! I've adjusted the wording a little; here is the exact patch. OK to commit? Mark Index: svnwrite.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v retrieving revision 1.11 diff -U3 -r1.11 svnwrite.html --- svnwrite.html 18 May 2006 11:57:24 -0000 1.11 +++ svnwrite.html 24 May 2006 08:29:28 -0000 @@ -46,9 +46,14 @@ ssh-keygen program) and other details.

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 be able to check out a tree with SVN and add yourself to the -MAINTAINERS file to test write access, following the instructions below.

+gcc.gnu.org and inform you by mail. At this point, +check out a tree using the instructions below and add yourself +to the MAINTAINERS file. Then produce a diff to +that file and circulate it to the gcc-patches list, whilst also +checking in your change to test write access (approval from the mailing +list is not needed in this one case). For all other changes, please +be sure to follow the write access policies below. +

Setting up your local SVN tree