From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] New wiki page: http://wiki.qemu.org/Hosts
Date: Mon, 5 Dec 2016 06:01:00 -0500 (EST) [thread overview]
Message-ID: <107683828.1411160.1480935660208.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Zuu=R3r+PREsgvAfZM1NomqOH4RWVY8-=_Rpsq_PETQ@mail.gmail.com>
----- Original Message -----
> From: "Peter Maydell" <peter.maydell@linaro.org>
> To: "Paolo Bonzini" <pbonzini@redhat.com>
> Cc: "Programmingkid" <programmingkidx@gmail.com>, "qemu-devel qemu-devel" <qemu-devel@nongnu.org>
> Sent: Monday, December 5, 2016 11:57:04 AM
> Subject: Re: [Qemu-devel] New wiki page: http://wiki.qemu.org/Hosts
>
> On 3 December 2016 at 08:41, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > Since this stuff changes rarely, it should be in the source tree
> > instead. You can link to the source tree from the wiki with something
> > like this:
> >
> > {{src|path=BUILDING|description=the BUILDING file in the source tree}}
> >
> > Would you like to make a patch moving the information from the wiki to
> > such a file?
>
> How would this differ from the "Building" section in the README
> in the source tree?
Looking at the wiki pages, it would have information on how to get QEMU's
dependencies.
Paolo
next prev parent reply other threads:[~2016-12-05 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 22:59 [Qemu-devel] New wiki page: http://wiki.qemu.org/Hosts Programmingkid
2016-12-03 8:41 ` Paolo Bonzini
2016-12-03 16:23 ` Programmingkid
2016-12-05 9:15 ` Paolo Bonzini
2016-12-05 10:57 ` Peter Maydell
2016-12-05 11:01 ` Paolo Bonzini [this message]
2016-12-05 13:47 ` G 3
2016-12-05 14:15 ` Paolo Bonzini
2016-12-05 14:25 ` G 3
2016-12-05 15:23 ` Paolo Bonzini
2016-12-03 8:57 ` Thomas Huth
2016-12-03 16:30 ` Programmingkid
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=107683828.1411160.1480935660208.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--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).