From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: gdb-patches@sourceware.org, kevinb@redhat.com
Subject: Re: [PATCH v5 1/1] [gdb]: add git trailer information on gdb/MAINTAINERS
Date: Fri, 06 Oct 2023 14:11:20 +0300 [thread overview]
Message-ID: <835y3k2eg7.fsf@gnu.org> (raw)
In-Reply-To: <2fc45e96-1d00-076b-0dcd-37c9ca3f87f1@redhat.com> (message from Guinevere Larsen on Fri, 6 Oct 2023 09:39:01 +0200)
> Date: Fri, 6 Oct 2023 09:39:01 +0200
> Cc: gdb-patches@sourceware.org, kevinb@redhat.com
> From: Guinevere Larsen <blarsen@redhat.com>
>
> On 05/10/2023 18:01, Eli Zaretskii wrote:
> >> + This tag is also often described as "partial approval"
> >> + Usage: "Acked-By: Your Name <your@email> (area)"
> > What are the possible "area"s? And how to indicate more than a single
> > area?
> "area of GDB" is used throughout the maintainers file without being
> specified anywhere, such as when explaining "Authorized Comitters":
> - The Authorized Committers.
>
> These are developers who are trusted to make changes within a specific
> area of GDB without additional oversight.
>
> And all throughout the "Responsible maintainers" section. So I think it
> is understood well enough, especially since it is expected that the
> reviewers are the ones who should know if the patch touches multiple
> areas and so on.
Fine by me, but then I think the text describing the tags should say
explicitly that the areas are those mentioned elsewhere in the
document.
> > And a more general question: when the review comments are minor, we
> > are used to say something like "okay with those nits fixed", meaning
> > that there's no need for posting another version of the patch before
> > committing it "with those nits fixed". Is this an
> > Acked-By/Approved-By or Reviewed-By?
>
> The tags are just ways to make your intent obvious. If you were
> approving the patch "with the nits fixed", you use Approved-By, if you
> were approving only parts of the patch, use Acked-by, and if you think
> the patch is ok but can't/won't approve, use Reviewed-By.
I think this should also be in the document explicitly.
Thanks.
next prev parent reply other threads:[~2023-10-06 11:11 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 [this message]
2023-10-05 17:55 ` Kevin Buettner
2023-10-09 9:59 ` Guinevere Larsen
2023-10-10 15:14 ` Simon Marchi
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=835y3k2eg7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
/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).