From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] internal_error: remove need to pass __FILE__/__LINE__
Date: Wed, 19 Oct 2022 15:47:58 +0100 [thread overview]
Message-ID: <5834f5eb-5691-cf1f-6825-05388a1d3896@palves.net> (raw)
In-Reply-To: <3c9d3f9d-1e1a-795b-242e-f3a3ee9dcb6f@simark.ca>
On 2022-10-18 3:53 p.m., Simon Marchi wrote:
>> I'll just go with Approved-By. However, I don't know which of 3 email addresses
>> you've been using would you like to be put in the tags. :-) I guess the one
>> listed in gdb/MAINTAINERS should be canonical?
>
> Haha, good question. Given that most of my time spent working on GDB is
> for work, and not on my own time anymore, it should probably be my work
> address, so go with the @efficios.com one. I'll update MAINTAINERS to
> reflect that.
Done, and pushed.
next prev parent reply other threads:[~2022-10-19 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 18:50 Pedro Alves
2022-10-17 18:59 ` Simon Marchi
2022-10-17 19:26 ` Pedro Alves
2022-10-17 19:27 ` Simon Marchi
2022-10-17 19:37 ` Pedro Alves
2022-10-17 19:45 ` Simon Marchi
2022-10-18 11:15 ` Pedro Alves
2022-10-18 14:53 ` Simon Marchi
2022-10-19 14:47 ` Pedro Alves [this message]
2022-10-18 12:34 ` Bruno Larsen
2022-10-18 14:55 ` Simon Marchi
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=5834f5eb-5691-cf1f-6825-05388a1d3896@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).