public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Guinevere Larsen <blarsen@redhat.com>,
	Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org, Pedro Alves <pedro@palves.net>
Subject: Re: [PATCH v5 1/1] [gdb]: add git trailer information on gdb/MAINTAINERS
Date: Tue, 10 Oct 2023 11:14:26 -0400	[thread overview]
Message-ID: <7993630f-6098-4d81-af02-ad4f73c20f1c@simark.ca> (raw)
In-Reply-To: <ade15d6a-5370-956c-d629-380cc418e268@redhat.com>

On 10/9/23 05:59, Guinevere Larsen wrote:
> I understand what you mean, and I see where I may have misunderstood when I said that "Acked-By" worked as partial review in QEMU.
> 
> I'm fine with this being the default if everyone agrees with it. To summarize informally, the tags would be like this:
> 
> * Acked-By: A maintainer of a certain area looked at the patch description and is fine with its direction. this says nothing about the quality of the code. May be restricted to some areas of the code
> * Reviewed-By: A contributor has looked at the code and thinks it is good, but is not approving it for any reason. May be restricted to some areas of the code.
> * Approved-By: A maintainer has looked at the code and thinks that it is ready for upstreaming. May be restricted to some areas, and may be conditional on receiving a review or ack for some area(s).

I like this use of Acked-By, it matches the meaning I thought it had,
based on what other projects do.  It happens that we say something like
"I gave it a quick look and it looks fine to me", indicating that we did
not do a thorough review, in which case Acked-By is appropriate.

Simon

  reply	other threads:[~2023-10-10 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 11:35 [PATCH v5 0/1] update MAINTAINERS file with git trailers Guinevere Larsen
2023-10-05 11:35 ` [PATCH v5 1/1] [gdb]: add git trailer information on gdb/MAINTAINERS Guinevere Larsen
2023-10-05 14:31   ` Simon Marchi
2023-10-05 16:01   ` Eli Zaretskii
2023-10-06  7:39     ` Guinevere Larsen
2023-10-06 11:11       ` Eli Zaretskii
2023-10-05 17:55   ` Kevin Buettner
2023-10-09  9:59     ` Guinevere Larsen
2023-10-10 15:14       ` Simon Marchi [this message]
2023-10-26 12:46         ` Lancelot SIX
2023-10-25 14:34 ` [PING][PATCH v5 0/1] update MAINTAINERS file with git trailers Guinevere Larsen

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=7993630f-6098-4d81-af02-ad4f73c20f1c@simark.ca \
    --to=simark@simark.ca \
    --cc=blarsen@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --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).