From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Lluís Vilanova" <vilanova@ac.upc.edu>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] We need more reviewers/maintainers!!
Date: Wed, 14 Mar 2012 14:50:03 +0100 [thread overview]
Message-ID: <4F60A20B.2020108@suse.de> (raw)
In-Reply-To: <4F5F4B4F.3070003@redhat.com>
Am 13.03.2012 14:27, schrieb Avi Kivity:
> On 03/12/2012 08:18 PM, Stefano Stabellini wrote:
>>>
>>> * Reviewed-by: Full Name <email>
>>>
>>> A Reviewed-by tag is a statement of opinion that the patch is an appropriate
>>> modification without any remaining serious technical issues. Any interested
>>> reviewer (who has done the work) can offer a Reviewed-by tag for a patch.
>>>
>>>
>>> My understanding until now was that both Acked-by and Reviewed-by were tags
>>> reserved to people with privileges to write into the repository.
>>
>> Anybody should be allowed to give his own Acked-by or Reviewed-by, not
>> just maintainers. Of course an acked-by from the maintainer of the area
>> the patch is touching has a different weight.
>
> To me, an Ack is reserved for people who have authority in an area,
> either by being the formal maintainer of the subsystem, or by just being
> an expert in that area. An Acked-by short-circuit's the following exchange:
>
> Author: submit patch P
> Maintainer: P touches subsystem X, what do Expert E and sub-maintainer
> M have to say about it?
> E, M: looks okay
>
> The acked-by allows the maintainer to skip the exchange. Of course
> usually patches should go through a submaintainer tree, but sometimes
> this is not feasible, either because there is no tree for that area, or
> because the patch or patchset touches many subsystems.
>
> So an ack should come from people who expect to be asked about the patch.
The way I saw it, Acked-by means that the person asserts that the
contents of the change is sensible, and when I use it I either tested it
myself or am absolutely sure it doesn't break the build.
Reviewed-by I use by comparison to assert that a patch reasonably
conforms to our Coding guidelines, has an SoB and does nothing obviously
stupid but that I did not bother to smoke-test on my system.
What I have wondered is, is there any semantic difference between "Ack",
"Acked", "ACK" and "Acked-by: name <email>"? I.e., when someone replies
with "Ack", should one document that as an Acked-by for a PULL?
Similarly, should "Looks good." be translated to Reviewed-by or does it
mean less?
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-14 13:50 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 17:06 [Qemu-devel] We need more reviewers/maintainers!! Stefano Stabellini
2012-03-12 17:16 ` Anthony Liguori
2012-03-12 17:34 ` Stefano Stabellini
2012-03-12 18:48 ` Anthony Liguori
2012-03-12 19:10 ` Stefano Stabellini
2012-03-12 19:04 ` Anthony Liguori
2012-03-12 19:21 ` Stefano Stabellini
2012-03-12 19:38 ` Anthony Liguori
2012-03-13 11:34 ` Stefano Stabellini
2012-03-13 11:27 ` Kevin Wolf
2012-03-13 11:41 ` Stefano Stabellini
2012-03-13 12:12 ` Paolo Bonzini
2012-03-12 18:03 ` Lluís Vilanova
2012-03-12 18:10 ` Anthony Liguori
2012-03-12 19:39 ` Lluís Vilanova
2012-03-12 19:43 ` Anthony Liguori
2012-03-12 18:18 ` Stefano Stabellini
2012-03-13 13:27 ` Avi Kivity
2012-03-14 13:50 ` Andreas Färber [this message]
2012-03-14 13:52 ` Anthony Liguori
2012-03-14 13:58 ` Peter Maydell
2012-03-14 14:17 ` Anthony Liguori
2012-03-14 14:25 ` Andreas Färber
2012-03-13 10:38 ` Andreas Färber
2012-03-12 19:18 ` Michael Roth
2012-03-13 11:11 ` Stefano Stabellini
2012-03-12 20:12 ` Stefan Weil
2012-03-12 20:24 ` Peter Maydell
2012-03-12 20:29 ` Anthony Liguori
2012-03-12 20:43 ` Peter Maydell
2012-03-12 21:06 ` Anthony Liguori
2012-03-12 21:09 ` malc
2012-03-12 21:13 ` Anthony Liguori
2012-03-12 21:41 ` Stefan Weil
2012-03-12 21:52 ` Anthony Liguori
2012-03-12 21:43 ` malc
2012-03-12 21:49 ` Anthony Liguori
2012-03-12 22:53 ` malc
2012-03-12 21:16 ` Peter Maydell
2012-03-12 21:19 ` Anthony Liguori
2012-03-13 10:39 ` Stefan Hajnoczi
2012-03-12 20:40 ` Michael S. Tsirkin
2012-03-12 20:27 ` Anthony Liguori
2012-03-12 21:12 ` Stefan Weil
2012-03-12 21:18 ` Anthony Liguori
2012-03-12 23:32 ` Andreas Färber
2012-03-13 0:16 ` Anthony Liguori
2012-03-13 0:54 ` Alexander Graf
2012-03-13 1:01 ` Andreas Färber
2012-03-13 1:23 ` Alexander Graf
2012-03-13 1:31 ` Super Bisquit
2012-03-13 1:39 ` Anthony Liguori
2012-03-13 2:04 ` Alexander Graf
2012-03-13 2:05 ` Anthony Liguori
2012-03-14 19:47 ` Blue Swirl
2012-03-13 9:09 ` Peter Maydell
2012-03-13 13:50 ` Avi Kivity
2012-03-13 14:12 ` Peter Maydell
2012-03-13 14:39 ` Avi Kivity
2012-03-13 14:43 ` Anthony Liguori
2012-03-13 14:46 ` Alexander Graf
2012-03-13 14:54 ` Peter Maydell
2012-03-13 14:49 ` Andreas Färber
2012-03-13 14:57 ` Avi Kivity
2012-03-13 15:13 ` Eric Blake
2012-03-12 21:24 ` Stefan Weil
2012-03-13 13:40 ` Avi Kivity
2012-03-13 14:00 ` Anthony Liguori
2012-03-13 14:38 ` Avi Kivity
2012-03-13 14:41 ` Anthony Liguori
2012-03-14 20:00 ` Blue Swirl
2012-03-14 19:55 ` Blue Swirl
2012-03-13 10:41 ` Stefan Hajnoczi
2012-03-13 16:31 ` Andreas Färber
2012-03-13 18:14 ` Stefan Weil
2012-03-14 9:17 ` Stefan Hajnoczi
2012-07-18 9:28 ` Peter Maydell
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=4F60A20B.2020108@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vilanova@ac.upc.edu \
/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.