qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1338563 <1338563@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1338563] Re: README refers to a non-extant file
Date: Mon, 7 Jul 2014 19:17:21 +0100	[thread overview]
Message-ID: <CAFEAcA8OuvrCOpRNpu93d4SibGF=gEbuZmXd9oQH=khrvFFNew@mail.gmail.com> (raw)
In-Reply-To: <20140707175710.9284.54663.malone@wampee.canonical.com>

On 7 July 2014 18:57, Stefan Weil <1338563@bugs.launchpad.net> wrote:
> The QEMU wiki which is mentioned in the README includes documention, and
> there is a link to qemu-doc.html on http://wiki.qemu-project.org/Manual.

This is true, but I think it would be helpful if we specifically pointed the
user there for the how-to-compile-from-source instructions, since it's
otherwise not very obvious.

In fact, the "compilation from source" section of qemu-doc.texi is
pretty badly out of date in several ways. It would probably be better
to extract it into a separate COMPILING plain text file, since it's
also not very friendly to require somebody compiling QEMU to have
either network access or to read raw .texi sources (and conversely
if you've got a pre-compiled QEMU then you don't have any interest
in reading stuff about configure and make).

thanks
-- PMM

  reply	other threads:[~2014-07-07 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 12:44 [Qemu-devel] [Bug 1338563] [NEW] README refers to a non-extant file Daniel U. Thibault
2014-07-07 13:47 ` [Qemu-devel] [Bug 1338563] " Paolo Bonzini
2014-07-07 17:24 ` Daniel U. Thibault
2014-07-07 17:57 ` Stefan Weil
2014-07-07 18:17   ` Peter Maydell [this message]
2014-07-16 19:18 ` Daniel U. Thibault
2020-11-04 19:37 ` John Snow
2020-11-05  9:05 ` Thomas Huth

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='CAFEAcA8OuvrCOpRNpu93d4SibGF=gEbuZmXd9oQH=khrvFFNew@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=1338563@bugs.launchpad.net \
    --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).