From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org, xen-devel@lists.xen.org,
"Paul Durrant" <paul.durrant@citrix.com>,
"Stefano Stabellini" <stefano.stabellini@citrix.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v5] Xen PV Device
Date: Mon, 08 Jul 2013 10:12:52 -0500 [thread overview]
Message-ID: <878v1h3x1n.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA9sQXSEvTSU8JpPQV8kSsVrqg0zv5-P=w8o9Ei8WZTwUA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 8 July 2013 15:04, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> (Just a nit and responding because this happens commonly).
>>
>> You probably mean Reviewed-by. Acked-by really means, "I am not the
>> maintainer of this area, I have not reviewed this patch, but I am
>> generally okay with the idea as best I can tell."
>
> Don't you mean "I *am* the maintainer of this area" ?
No. It's "this looks okay to me". A maintainer would be expected to do
a more thorough review than just a first pass "this looks okay to me."
> I've always
> assumed it means "as the maintainer I have a potential veto over
> this code change and I am explicitly not exercising it even though
> I may not have done a complete review and/or test"...
"As *a* maintainer". It's basically, "my opinion here matters so I'm
going to voice my approval." It's not limited to maintainers though.
>> It's a very low vote of confidence. I wouldn't apply a patch that only
>> had Acked-bys.
>>
>> OTOH, Reviewed-by means, "I have reviewed the patch and believe it works
>> as described and meets project guidelines". Based on your review of V4,
>> pretty sure that's what you mean here.
>>
>> https://github.com/torvalds/linux/blob/master/Documentation/SubmittingPatches#L392
>>
>> The distinction matters in practice because I have scripts to track
>> patches based on whether they've received Reviewed-bys or not. I'm
>> often running into cases where people are Acked-by'ing instead of
>> Reviewed-by'ing patches and then wondering why they haven't gotten
>> merged...
>
> I think Andreas is the major exponent of the idea that "acked-by"
> is stronger than "reviewed-by". Regardless, I think we should
> standardise on what we mean by both tags. (Alas the kernel docs
> are not entirely clear about acked-by, though the meaning of
> reviewed-by is certainly clear.)
That's why I referred to them. They seem clear to me. Suggestions for
improvement are welcome of course :-)
Regards,
Anthony Liguori
>
> thanks
> -- PMM
next prev parent reply other threads:[~2013-07-08 15:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 9:30 [Qemu-devel] [PATCH v5] Xen PV Device Paul Durrant
2013-07-04 12:52 ` Stefano Stabellini
2013-07-04 12:52 ` Stefano Stabellini
2013-07-05 21:44 ` [Qemu-devel] [Xen-devel] " Matt Wilson
2013-07-05 21:44 ` Matt Wilson
2013-07-08 14:04 ` [Qemu-devel] " Anthony Liguori
2013-07-08 14:04 ` Anthony Liguori
2013-07-08 14:10 ` Peter Maydell
2013-07-08 14:19 ` Alex Bligh
2013-07-08 14:19 ` Alex Bligh
2013-07-08 14:48 ` Andreas Färber
2013-07-08 14:48 ` Andreas Färber
2013-07-08 15:20 ` Anthony Liguori
2013-07-08 15:34 ` Peter Maydell
2013-07-08 15:34 ` Peter Maydell
2013-07-08 16:02 ` Andreas Färber
2013-07-08 16:02 ` Andreas Färber
2013-07-08 16:37 ` Stefano Stabellini
2013-07-08 16:42 ` Stefano Stabellini
2013-07-08 16:42 ` Stefano Stabellini
2013-07-08 17:31 ` Anthony Liguori
2013-07-09 10:29 ` Stefano Stabellini
2013-07-09 10:29 ` Stefano Stabellini
2013-07-08 17:31 ` Anthony Liguori
2013-07-08 16:37 ` Stefano Stabellini
2013-07-08 15:20 ` Anthony Liguori
2013-07-08 15:12 ` Anthony Liguori [this message]
2013-07-08 15:12 ` Anthony Liguori
2013-07-08 14:10 ` Peter Maydell
2013-07-08 14:08 ` Anthony Liguori
2013-07-08 14:08 ` Anthony Liguori
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=878v1h3x1n.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=paul.durrant@citrix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.