qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, quintela@redhat.com, knoel@redhat.com,
	mrhines@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com,
	gokul@us.ibm.com, chegu_vinod@hp.com
Subject: Re: [Qemu-devel] [PATCH v12 15/15] rdma: account for the time spent in MIG_STATE_SETUP through QMP
Date: Fri, 28 Jun 2013 07:32:03 -0600	[thread overview]
Message-ID: <51CD9053.1090106@redhat.com> (raw)
In-Reply-To: <51CD37F8.7070807@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]

On 06/28/2013 01:15 AM, Paolo Bonzini wrote:
> Il 28/06/2013 00:58, Eric Blake ha scritto:
>>> Using the previous patches, we're now able to timestamp the
>>> SETUP state. Once we have this time, let the user know about it
>>> in the schema.
>>>
>>> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by:
>>> Michael R. Hines <mrhines@us.ibm.com>
> 
>> Usually, Reviewed-by lines are listed _after_ S-o-b lines -
>> signature lines are typically chronological, but the patch has to
>> be signed before a review can have any weight at getting the patch
>> into a pull request :)
> 
> Hmm, that's not how I understood it.  The last line in the message
> should be S-o-b.  If _I_ collect the Reviewed-bys when committing, I'll do
> 
> Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
> Reviewed-by: Juan Quintela <quintela@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

That's what I meant by signatures being chronological.  The _first_ line
is Michael's s-o-b, since he wrote it; on any of Michael's respins where
he adds signatures collected during the review process (which will only
be reviewed-by or tested-by - here a review from Juan), those come next;
then when the maintainer incorporates the patch into a pull request,
further signatures are collected (any reviewed-by that were not
incorporated by Michael because no respin was required, followed by the
final s-o-b saying the maintainer modified the commit message as part of
incorporating into the pull request).

> But since Michael is the one collecting the tags from previous
> submissions of the patch series, he's placing it right.

Having Michael's s-o-b last, after reviewed-by picked up from earlier
revisions, is not chronological.  Maintainers add reviewed-by before
their own s-o-b, but only because their s-o-b is a secondary s-o-b; I
still don't see why the original author would add reviewed-by before
their (lone) s-o-b.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  parent reply	other threads:[~2013-06-28 13:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26  1:35 [Qemu-devel] [PATCH v12 00/15] rdma: migration support mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 01/15] rdma: add documentation mrhines
2013-06-26  1:48   ` [Qemu-devel] [PATCH v12 00/15] rdma: migration support Michael R. Hines
2013-06-27 22:41   ` [Qemu-devel] [PATCH v12 01/15] rdma: add documentation Eric Blake
2013-06-27 22:48     ` Michael R. Hines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 02/15] rdma: introduce qemu_update_position() mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 03/15] rdma: export yield_until_fd_readable() mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 04/15] rdma: export throughput w/ MigrationStats QMP mrhines
2013-06-27 23:02   ` Eric Blake
2013-06-28 13:13     ` Michael R. Hines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 05/15] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 06/15] rdma: export qemu_fflush() mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 08/15] rdma: introduce qemu_ram_foreach_block() mrhines
2013-06-27 19:24   ` Peter Maydell
2013-06-27 19:56     ` Michael R. Hines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 09/15] rdma: new QEMUFileOps hooks mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 10/15] rdma: introduce capability x-rdma-pin-all mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 11/15] rdma: core logic mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 12/15] rdma: send pc.ram mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 13/15] rdma: allow state transitions between other states besides ACTIVE mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 14/15] rdma: introduce MIG_STATE_NONE and change MIG_STATE_SETUP state transition mrhines
2013-06-26  1:35 ` [Qemu-devel] [PATCH v12 15/15] rdma: account for the time spent in MIG_STATE_SETUP through QMP mrhines
2013-06-27 22:58   ` Eric Blake
2013-06-28  7:15     ` Paolo Bonzini
2013-06-28 13:15       ` Michael R. Hines
2013-06-28 13:32       ` Eric Blake [this message]
2013-06-28 14:45         ` Michael R. Hines
2013-06-28 13:14     ` Michael R. Hines

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=51CD9053.1090106@redhat.com \
    --to=eblake@redhat.com \
    --cc=abali@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=chegu_vinod@hp.com \
    --cc=gokul@us.ibm.com \
    --cc=knoel@redhat.com \
    --cc=mrhines@linux.vnet.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).