From: Simon Marchi <simark@simark.ca>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Update my email address in MAINTAINERS
Date: Sat, 3 Dec 2022 12:50:27 -0500 [thread overview]
Message-ID: <7ed4fcd9-caa4-a6d6-5bc4-74a0a233874c@simark.ca> (raw)
In-Reply-To: <20221203000129.421292-1-thiago.bauermann@linaro.org>
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
next prev parent reply other threads:[~2022-12-03 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 0:01 Thiago Jung Bauermann
2022-12-03 17:50 ` Simon Marchi [this message]
2022-12-05 14:04 ` Thiago Jung Bauermann
2022-12-05 14:07 ` Luis Machado
2022-12-05 16:02 ` Thiago Jung Bauermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ed4fcd9-caa4-a6d6-5bc4-74a0a233874c@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).