Message ID | 20171221152628.12942-1-kwolf@redhat.com |
---|---|
State | New |
Headers | show |
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. The UTF-8 one is longstanding and ignorable, but the other two are new. thanks -- PMM
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. Kevin
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