From: Alex Bligh <alex@alex.org.uk>
To: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <anthony@codemonkey.ws>
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>,
"Alex Bligh" <alex@alex.org.uk>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v5] Xen PV Device
Date: Mon, 08 Jul 2013 15:19:43 +0100 [thread overview]
Message-ID: <FE52EED476960CEBBF7C01D9@Ximines.local> (raw)
In-Reply-To: <CAFEAcA9sQXSEvTSU8JpPQV8kSsVrqg0zv5-P=w8o9Ei8WZTwUA@mail.gmail.com>
--On 8 July 2013 15:10:49 +0100 Peter Maydell <peter.maydell@linaro.org>
wrote:
>> 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"...
Really? That would imply no one should add Acked-By except
maintainers. That's not right according to:
https://github.com/torvalds/linux/blob/master/Documentation/SubmittingPatches#L397
The use at line 401 by maintainers does not seem to me to be 'exclusive'.
For instance, I've used Acked-by when someone else modifies a piece
of code I've contributed (e.g. to fix a bug), to indicate I agree
with them.
It's also pretty clear (line 437 and 462) what Reviewed-by: means
--
Alex Bligh
next prev parent reply other threads:[~2013-07-08 14:19 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 ` Matt Wilson
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:10 ` Peter Maydell
2013-07-08 14:19 ` Alex Bligh [this message]
2013-07-08 14:19 ` Alex Bligh
2013-07-08 14:48 ` Andreas Färber
2013-07-08 15:20 ` Anthony Liguori
2013-07-08 15:20 ` Anthony Liguori
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 15:34 ` Peter Maydell
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 14:48 ` Andreas Färber
2013-07-08 15:12 ` Anthony Liguori
2013-07-08 15:12 ` Anthony Liguori
2013-07-08 14:04 ` Anthony Liguori
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=FE52EED476960CEBBF7C01D9@Ximines.local \
--to=alex@alex.org.uk \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--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.