public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Bruno Larsen <blarsen@redhat.com>, Pedro Alves <pedro@palves.net>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] internal_error: remove need to pass __FILE__/__LINE__
Date: Tue, 18 Oct 2022 10:55:22 -0400	[thread overview]
Message-ID: <0021d003-f807-b28f-4b76-bfcd055b169f@simark.ca> (raw)
In-Reply-To: <1ba52d6f-8789-e05f-09e3-21ed7fbc2e0e@redhat.com>

On 10/18/22 08:34, Bruno Larsen via Gdb-patches wrote:
> 
> On 17/10/2022 21:45, Simon Marchi via Gdb-patches wrote:
>> Heh, I forgot to look at the code.  It all looks good, except black
>> reformats gdbarch.py for me here.  With that fixed you can add my
>> Reviewed-By or Approved-By (not sure which one we use when someone who
>> can approve a patch reviews the patch of someone else who can approve).
> 
> I would suggest Pedro use the Approved-by tag. Preferably the approver of the patch should be different to the submitter.
> 
> My thought process for someone who can approve using a reviewed-by tag is if you don't know enough for the area of code but you did look at the patch and saw nothing wrong with it. About the same situation when you'd say "this patch looks good to me but I'd defer to XXX, who knows this better" before we started using tags.

Thanks, that makes sense.

In the case of reviewing Pedro's patches, we would need a tag to say "It
looks good, I don't think I understand it all, but given that Pedro
wrote the patch, it's most likely correct" :).

Simon

      reply	other threads:[~2022-10-18 14:55 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
2022-10-18 12:34           ` Bruno Larsen
2022-10-18 14:55             ` Simon Marchi [this message]

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=0021d003-f807-b28f-4b76-bfcd055b169f@simark.ca \
    --to=simark@simark.ca \
    --cc=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).