From: Eric Blake <eblake@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Dmitry Mishin <dim@virtuozzo.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/1] doc: document chardev option 'append'
Date: Tue, 22 Dec 2015 08:53:04 -0700 [thread overview]
Message-ID: <567971E0.4020603@redhat.com> (raw)
In-Reply-To: <1450777749-14022-1-git-send-email-den@openvz.org>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On 12/22/2015 02:49 AM, Denis V. Lunev wrote:
> commit 31e38a22a0c5a25646f966f001e1f5513d5a186d
> Author: Olga Krishtal <okrishtal@virtuozzo.com>
> Date: Fri Dec 4 09:42:04 2015 +0300
>
> qemu-char: append opt to stop truncation of serial file
>
> has added the option to the runtime but does not added it to -help
> output. This blocks libvirt from using it.
In addition to Dan's comment about the dead sentence,
> +@option{append} specifies that QEMU must truncate the file on open.
> +@option{append} is optional, default value is off.
This is backwards. It should read something more like:
@option{append} specifies that QEMU should append to the file. It
defaults to off, for truncating the file instead of appending.
Or maybe:
@option{append} controls whether QEMU truncates the file (default if
omitted, or if specified as off), or appends to the file (specified as on).
Check if there are other similar wordings to borrow from.
--
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: 604 bytes --]
prev parent reply other threads:[~2015-12-22 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 9:49 [Qemu-devel] [PATCH v2 1/1] doc: document chardev option 'append' Denis V. Lunev
2015-12-22 10:26 ` Daniel P. Berrange
2015-12-22 10:39 ` Denis V. Lunev
2015-12-22 15:53 ` 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=567971E0.4020603@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dim@virtuozzo.com \
--cc=pbonzini@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).