qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/13] Block layer patches
Date: Tue, 26 Dec 2017 10:53:29 +0800	[thread overview]
Message-ID: <20171226025329.GE9418@lemon> (raw)
In-Reply-To: <20171222133128.GF3763@localhost.localdomain>

On Fri, 12/22 14:31, Kevin Wolf wrote:
> Am 21.12.2017 um 23:47 hat Peter Maydell geschrieben:
> > On 21 December 2017 at 15:26, Kevin Wolf <kwolf@redhat.com> wrote:
> > > The following changes since commit 4da5c51cac8363f86ec92dc99c38f9382d617647:
> > >
> > >   Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2017-12-20' into staging (2017-12-20 20:38:36 +0000)
> > >
> > > are available in the git repository at:
> > >
> > >   git://repo.or.cz/qemu/kevin.git tags/for-upstream
> > >
> > > for you to fetch changes up to af65cdae56861d5e163559a53f7ec34142a249f1:
> > >
> > >   nvme: Add tracing (2017-12-21 16:02:14 +0100)
> > >
> > > ----------------------------------------------------------------
> > > Block layer patches
> > >
> > > ----------------------------------------------------------------
> > 
> > Now I get these warnings on NetBSD/OpenBSD/OSX:
> > 
> >   GEN     qemu-doc.txt
> > /root/qemu/qemu-doc.texi:8: warning: unrecognized encoding name `UTF-8'.
> > /root/qemu//qemu-img.texi:61: warning: unlikely character ( in @var.
> > /root/qemu//qemu-img.texi:61: warning: unlikely character ) in @var.
> 
> Fam, I'm dropping "qemu-img: Document --force-share / -U" from my pull
> request again.
> 
> The problem there seems to be that we're inside of a '@table @var' here.
> People have been careless enough to add options in there, which results
> in less than optimal formatting in the manpage.
> 
> I'd suggest that we split the table in two, first a '@table @var' that
> explains only variables, and after that a proper '@table @option' for
> the options. I suppose (and hope) that in '@table @option', parentheses
> are allowed.

Sounds good. Thank you, v5 sent.

Fam

      reply	other threads:[~2017-12-26  2:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 15:26 [Qemu-devel] [PULL v2 00/13] Block layer patches Kevin Wolf
2017-12-21 22:47 ` Peter Maydell
2017-12-22 13:31   ` Kevin Wolf
2017-12-26  2:53     ` Fam Zheng [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=20171226025329.GE9418@lemon \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --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).