From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2906 invoked by alias); 11 Nov 2009 02:00:42 -0000 Received: (qmail 2690 invoked by uid 22791); 11 Nov 2009 02:00:40 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Nov 2009 02:00:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id B030F2BABC2; Tue, 10 Nov 2009 21:00:30 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id C3NibAvTge7q; Tue, 10 Nov 2009 21:00:30 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 4EBB72BAC1A; Tue, 10 Nov 2009 21:00:30 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 65711F5905; Tue, 10 Nov 2009 18:00:13 -0800 (PST) Date: Thu, 12 Nov 2009 01:00:00 -0000 From: Joel Brobecker To: Daniel Gutson Cc: gdb@sourceware.org Subject: Re: write after approval privs request Message-ID: <20091111020013.GJ11716@adacore.com> References: <4AFA0CF3.1080208@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AFA0CF3.1080208@codesourcery.com> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00128.txt.bz2 > since I'm submitting a number of patches, could I have write after > approval privs, so I don't bother other people asking to commit those > for me? Of course. Do you have an account on sourceware.org? If not, please fill in the following form. You can list me as your sponsor. This should get you all setup for write access very quickly. Once you have write access, checkout the sources, and commit a change to gdb/MAINTAINERS that adds you to the Write After Approval list. This is a good way to verify that your write access works. Please be sure to send the corresponding patch, with ChangeLog, to gdb-patches. Welcome to the group, -- Joel