All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, John Snow <jsnow@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] README: fill out some useful quickstart information
Date: Tue, 22 Sep 2015 22:15:25 +0200	[thread overview]
Message-ID: <5601B6DD.5070508@redhat.com> (raw)
In-Reply-To: <871tdqrhqq.fsf@blackfin.pond.sub.org>



On 22/09/2015 10:16, Markus Armbruster wrote:
>> "To build QEMU, you'd generally [some basic steps that have generally
>> worked for a long time], but for up-to-date authoritative information,
>> please do:
>>
>> mkdir path_to/build_dir
>> cd path_to/build_dir
>> ../../configure
>> make qemu-doc.html"
>>
>> We wind up documenting how to almost do a build anyway.

I don't think this is necessary.  We should remove duplicate information
from qemu-doc.texi, developer documentation doesn't belong in manuals.

Paolo

  reply	other threads:[~2015-09-22 20:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 11:03 [Qemu-devel] [PATCH] README: fill out some useful quickstart information Daniel P. Berrange
2015-09-17 11:32 ` Peter Maydell
2015-09-17 12:05   ` Daniel P. Berrange
2015-09-17 12:20     ` Peter Maydell
2015-09-17 12:36       ` Daniel P. Berrange
2015-09-17 12:40         ` Peter Maydell
2015-09-17 16:43         ` Markus Armbruster
2015-09-21 19:23           ` John Snow
2015-09-22  8:16             ` Markus Armbruster
2015-09-22 20:15               ` Paolo Bonzini [this message]
2015-09-23  9:52                 ` Markus Armbruster
2015-09-23 10:00                   ` Paolo Bonzini
2015-09-23 10:12                     ` Daniel P. Berrange
2015-09-17 11:44 ` Paolo Bonzini
2015-09-21 19:15 ` John Snow

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=5601B6DD.5070508@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@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.