From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@citrix.com>,
qemu-devel@nongnu.org, Paul Durrant <paul.durrant@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH v5] Xen PV Device
Date: Mon, 08 Jul 2013 10:20:21 -0500 [thread overview]
Message-ID: <8761wl3wp6.fsf@codemonkey.ws> (raw)
In-Reply-To: <51DAD155.3010106@suse.de>
Andreas Färber <afaerber@suse.de> writes:
> Am 08.07.2013 16:10, schrieb Peter Maydell:
>> 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" ? 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"...
>
> I think Anthony was referring to: if I am the maintainer I don't usually
> put tags on patches but pick them up and add my Signed-off-by.
> (Possible exception: when only part of a series is good and you don't
> feel like cherry-picking from it.)
Right, it goes:
1) Acked-by:
I haven't reviewed the code in detail but the general idea seems sane.
2) Reviewed-by:
The general idea seems sane, and I have done a thorough review of the
patch in question.
3) Signed-off-by:
All of the above, plus I have ensured that the code is of good quality,
does not break things, and the other things expected of a maintainer.
This is considered to be a legally binding statement too based on the
DCO so be aware of that and ensure you have the right approval to make
such a statement.
Semantics aside, let me be clear. If you want a patch to be merged,
you need to do a Reviewed-by.
Acked-by is not good enough to get something merged on its own.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2013-07-08 15:20 UTC|newest]
Thread overview: 16+ 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-05 21:44 ` [Qemu-devel] [Xen-devel] " Matt Wilson
2013-07-08 14:04 ` [Qemu-devel] " Anthony Liguori
2013-07-08 14:10 ` Peter Maydell
2013-07-08 14:19 ` Alex Bligh
2013-07-08 14:48 ` Andreas Färber
2013-07-08 15:20 ` Anthony Liguori [this message]
2013-07-08 15:34 ` Peter Maydell
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 17:31 ` Anthony Liguori
2013-07-09 10:29 ` Stefano Stabellini
2013-07-08 15:12 ` 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=8761wl3wp6.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 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 NNTP newsgroup(s).