qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qapi: Fix some blockdev-add documentation regressions
Date: Tue, 23 May 2017 12:26:32 -0500	[thread overview]
Message-ID: <9cd9abf4-37a3-b0ff-f208-d911ea9ac4db@redhat.com> (raw)
In-Reply-To: <76e4af58-9642-d1c5-39a8-f39c6c6d0240@redhat.com>

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

On 05/23/2017 09:32 AM, Eric Blake wrote:
> On 05/23/2017 03:39 AM, Markus Armbruster wrote:
>> Eric Blake <eblake@redhat.com> writes:
>>
>>> In the process of getting rid of docs/qmp-commands.txt, we
>>> managed to regress on any text that changed after the point
>>> where the move was first branched and when the move actually
>>> occurred.  For example, commit 3282eca for blockdev-snapshot
>>> re-added the extra "options" layer which had been cleaned up
>>> in commit 0153d2f.
>>>

> 
> I'll post a v2, since I have another pending doc patch that hasn't been
> reviewed yet, and since your audit means I need to update my commit
> message anyway.

Actually, it just got queued as trivial:
https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg05323.html

although git handles things just fine if it goes in earlier through any
other tree.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


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

      reply	other threads:[~2017-05-23 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 21:36 [Qemu-devel] [PATCH] qapi: Fix some blockdev-add documentation regressions Eric Blake
2017-05-23  8:39 ` Markus Armbruster
2017-05-23 14:32   ` Eric Blake
2017-05-23 17:26     ` Eric Blake [this message]

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=9cd9abf4-37a3-b0ff-f208-d911ea9ac4db@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.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).