All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Marc-André Lureau" <mlureau@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16
Date: Tue, 24 Jan 2017 10:53:07 +0100	[thread overview]
Message-ID: <87mvegu6m4.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA-fSJ5PfpKFaehruzjidBtmQP_435WLqgSLg=cQiETR8Q@mail.gmail.com> (Peter Maydell's message of "Fri, 20 Jan 2017 14:39:37 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> On 17 January 2017 at 16:43, Peter Maydell <peter.maydell@linaro.org> wrote:
>> In any case, applied this pullreq to master.
>
> Although it works fine on my OSX box (with warnings) it seems
> to have broken the Travis OSX builds:
> https://travis-ci.org/qemu/qemu/jobs/192750574
>
>   GEN     qemu-options.texi
>   GEN     qemu-monitor.texi
>   GEN     qemu-img-cmds.texi
>   GEN     qemu-monitor-info.texi
>   GEN     qemu-doc.txt
> qemu-doc.texi:7: warning: unrecognized encoding name `UTF-8'.
>   GEN     qemu-img.1
> /Users/travis/build/qemu/qemu//qemu-options.texi:60: warning: unlikely
> character [ in @var.
> /Users/travis/build/qemu/qemu//qemu-options.texi:60: warning: unlikely
> character ] in @var.
> /Users/travis/build/qemu/qemu//qemu-options.texi:61: warning: unlikely
> character [ in @var.
> /Users/travis/build/qemu/qemu//qemu-options.texi:61: warning: unlikely
> character ] in @var.
> /Users/travis/build/qemu/qemu//qemu-options.texi:630: No matching `@end table'.
> /Users/travis/build/qemu/qemu//qemu-doc.texi:1419: Cross reference to
> nonexistent node `bt-hcis' (perhaps incorrect sectioning?).
> makeinfo: Removing output file `qemu-doc.txt' due to errors; use
> --force to preserve.
> make: *** [qemu-doc.txt] Error 1

Are you *sure* this series causes the failure?

I generated qemu-options.texi for every merge commit since v2.8.0, and
the only one that changes it is commit 598cf1c "Merge remote-tracking
branch 'remotes/bonzini/tags/for-upstream' into staging".  I then
examined the commits in that merge, and the ones that affect
qemu-options.texi are:

* commit 43f187a hxtool: emit Texinfo headings as @subsection
* commit b0cb0a6 Plumb the HAXM-based hardware acceleration support

Could you kick off Travis builds to confirm or deny these commits cause
the OS X trouble?

  parent reply	other threads:[~2017-01-24  9:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  9:33 [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16 Markus Armbruster
2017-01-16 15:58 ` Peter Maydell
2017-01-17  8:31   ` Markus Armbruster
2017-01-17  9:54     ` Marc-André Lureau
2017-01-17 10:13       ` Markus Armbruster
2017-01-17 11:08     ` Peter Maydell
2017-01-17 12:08       ` Markus Armbruster
2017-01-17 12:24         ` Peter Maydell
2017-01-17 13:24           ` Markus Armbruster
2017-01-17 13:59             ` Peter Maydell
2017-01-17 14:15               ` Marc-André Lureau
2017-01-17 14:23               ` Markus Armbruster
2017-01-17 16:43                 ` Peter Maydell
2017-01-20 14:39                   ` Peter Maydell
2017-01-20 15:46                     ` Markus Armbruster
2017-01-20 15:48                       ` Peter Maydell
2017-01-23 12:48                         ` Alex Bennée
2017-01-23 13:59                       ` Daniel P. Berrange
2017-01-23 14:49                         ` Markus Armbruster
2017-01-24  9:53                     ` Markus Armbruster [this message]
2017-01-24 10:03                       ` Peter Maydell
2017-01-24 11:08                         ` Markus Armbruster
2017-01-24 10:09                       ` Markus Armbruster
2017-01-24 10:49                         ` Paolo Bonzini
2017-01-17 17:05         ` Eric Blake

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=87mvegu6m4.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=mlureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.