public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, apinski@marvell.com
Subject: Re: [PATCH 2/2] gdb/doc: uniformize wording for GMP and MPFR entries
Date: Tue, 14 Mar 2023 15:48:43 -0400	[thread overview]
Message-ID: <6a9c5a31-5b67-d684-5c57-07b4b1516318@gmail.com> (raw)
In-Reply-To: <83a60fruhx.fsf@gnu.org>

Hi Eli,

Le 2023-03-14 à 15:41, Eli Zaretskii a écrit :
>> From: Philippe Blain <levraiphilippeblain@gmail.com>
>> Cc: gdb-patches@sourceware.org, apinski@marvell.com
>> Date: Tue, 14 Mar 2023 13:38:08 -0400
>>
>> Le 2023-03-14 à 13:12, Philippe Blain a écrit :
>>> Hi Eli,
>>>
>> [...]
>>>
>>> I guess I was confused by the fact that 'Approved-by' is used here in a different way
>>> than in the Git project, where it is an explicit approval 
>>
>> I meant 'Reviewed-by' here, sorry.
> 
> Do they really use Reviewed-by as an approval?  _That_ would be
> confusing, since the word "review" means just that, it doesn't mean
> any approval.
> 

Yes, in the Git project, Reviewd-by is approval, see for example 
item 3. at https://git-scm.com/docs/SubmittingPatches#sign-off 
(under "If you like, you can put extra tags at the end"):


	Reviewed-by:, unlike the other tags, can only be offered by the 
	reviewers themselves when they are completely satisfied with the 
	patch after a detailed analysis.

This is in line with what it means for Linux also, as far as I understand [1].

Thanks,

Philippe.

[1] https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes

  reply	other threads:[~2023-03-14 19:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 17:46 [PATCH 0/2] doc: MPFR is now a necessary requirement Philippe Blain
2023-03-10 17:46 ` [PATCH 1/2] gdb/doc: " Philippe Blain
2023-03-10 19:15   ` Eli Zaretskii
2023-03-27 21:13   ` Simon Marchi
2023-03-29 17:21     ` Philippe Blain
2023-03-10 17:46 ` [PATCH 2/2] gdb/doc: uniformize wording for GMP and MPFR entries Philippe Blain
2023-03-10 19:17   ` Eli Zaretskii
2023-03-13 16:45     ` Philippe Blain
2023-03-14 12:08       ` Eli Zaretskii
2023-03-14 17:12         ` Philippe Blain
2023-03-14 17:38           ` Philippe Blain
2023-03-14 19:41             ` Eli Zaretskii
2023-03-14 19:48               ` Philippe Blain [this message]
2023-03-14 19:38           ` Eli Zaretskii
2023-03-27 21:18         ` Simon Marchi
2023-03-25 22:04 ` [PATCH 0/2] doc: MPFR is now a necessary requirement Philippe Blain
     [not found] ` <20230306-doc-require-mpfr-fix-v2-0-7de0f692b004@gmail.com>
     [not found]   ` <837cuqsbfb.fsf@gnu.org>
2023-04-07 13:19     ` [PATCH v2 " Philippe Blain

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=6a9c5a31-5b67-d684-5c57-07b4b1516318@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=apinski@marvell.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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).