From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 2zH6AHmMi2NqoR8AWB0awg (envelope-from ) for ; Sat, 03 Dec 2022 12:50:49 -0500 Received: by simark.ca (Postfix, from userid 112) id E7C171E124; Sat, 3 Dec 2022 12:50:48 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=yRskNJK5; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-9.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 4EEC71E0CB for ; Sat, 3 Dec 2022 12:50:48 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 9BE133858C36 for ; Sat, 3 Dec 2022 17:50:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9BE133858C36 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670089847; bh=yWmWinRQtmv3qhZ3EQJ8S83Qu9VggJN2h3vbyxo3R2Y=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=yRskNJK5lpRyvFF79DTtq3dzDtXGYbTV57jmyXYUl8Fl7P5TgAuDvxV6McLLYSziP TGZAvl5EimNpOacrjdD6Y0pmBlrpzGvnnmCxmyBKEh6hj8Rn1Aq7EcLf8HpTSQa9vL ZFKCL3xOIRZTxqdnuqC/ElDTfNVy526c4BcGzMYs= Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id A53A13858D39 for ; Sat, 3 Dec 2022 17:50:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A53A13858D39 Received: from [10.0.0.11] (unknown [217.28.27.60]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id EE67B1E0CB; Sat, 3 Dec 2022 12:50:27 -0500 (EST) Message-ID: <7ed4fcd9-caa4-a6d6-5bc4-74a0a233874c@simark.ca> Date: Sat, 3 Dec 2022 12:50:27 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [PATCH] gdb: Update my email address in MAINTAINERS Content-Language: en-US To: Thiago Jung Bauermann , gdb-patches@sourceware.org References: <20221203000129.421292-1-thiago.bauermann@linaro.org> In-Reply-To: <20221203000129.421292-1-thiago.bauermann@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 12/2/22 19:01, Thiago Jung Bauermann via Gdb-patches wrote: > --- > gdb/MAINTAINERS | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > Hello, > > A long time ago I had write after approval access to the GDB repo (it was > CVS back then, though!) but my last commit from that era was in 2012. > > I'm fortunate enough to be back to GDB development, and I have a few > patches approved lately so is it ok if I get back on the write after > approval list? > > Thanks, > Thiago Yes, of course. Updating one's email address can be considered "obvious", I'm sure. Simon