From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] README: fill out some useful quickstart information
Date: Wed, 23 Sep 2015 12:00:08 +0200 [thread overview]
Message-ID: <56027828.2090003@redhat.com> (raw)
In-Reply-To: <8737y5a2dt.fsf@blackfin.pond.sub.org>
On 23/09/2015 11:52, Markus Armbruster wrote:
> > I don't think this is necessary. We should remove duplicate information
> > from qemu-doc.texi, developer documentation doesn't belong in manuals.
>
> Just to avoid misunderstandings: I wouldn't object to splitting
> qemu-doc.texi into a user manual and developer documentation.
That really boils down to moving chapter 6 somewhere else; everything
else is user documentation. I think we should start with Dan's patch,
and then integrate it with any missing information from chapter 6.
Together with his build system docs, the non-texi developer
documentation is better than anything qemu-doc.texi has ever had
(*insert usual rant about perfect being the enemy of good*).
We also have the opposite problem (user documentation placed in docs/
instead of qemu-doc.texi) but that is separate.
Paolo
next prev parent reply other threads:[~2015-09-23 10:00 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
2015-09-23 9:52 ` Markus Armbruster
2015-09-23 10:00 ` Paolo Bonzini [this message]
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=56027828.2090003@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.