From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18416 invoked by alias); 15 Jan 2014 17:49:25 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 18406 invoked by uid 89); 15 Jan 2014 17:49:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,FM_IS_IT_OUR_ACCOUNT,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 15 Jan 2014 17:49:24 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s0FHnLMg002764 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Jan 2014 12:49:22 -0500 Received: from barimba (ovpn-113-85.phx2.redhat.com [10.3.113.85]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s0FHnJjY023878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 15 Jan 2014 12:49:20 -0500 From: Tom Tromey To: Will Newton Cc: Omair Javaid , Pedro Alves , "gdb-patches\@sourceware.org" Subject: Re: [PATCH v2 5/7] Adds support for thumb32 instructions recording References: <52CB0979.5090809@redhat.com> <52CE7B13.6040907@linaro.org> <52CE86B0.3020703@redhat.com> Date: Wed, 15 Jan 2014 17:49:00 -0000 In-Reply-To: (Will Newton's message of "Wed, 15 Jan 2014 17:27:10 +0000") Message-ID: <87vbxlqgo0.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2014-01/txt/msg00529.txt.bz2 Will> I'd like to recommend Omair be given commit privileges for future Will> patches if the maintainers agree. The rule is just if you have an assignment and have submitted one good patch, then you can get write-after-approval access. I'll send email about the details. Once you have your account it is customary to write a patch to MAINTAINERS, adding yourself to the write-after-approval section; then post the patch (w/ ChangeLog) as an FYI, then check it in. Tom