From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The new qemu.org
Date: Wed, 03 Feb 2010 13:27:34 -0600 [thread overview]
Message-ID: <4B69CE26.6010609@codemonkey.ws> (raw)
In-Reply-To: <2382D417-FEFF-4974-B705-C879CC8220C8@web.de>
On 02/03/2010 01:20 PM, Andreas Färber wrote:
>
> Am 03.02.2010 um 15:15 schrieb Anthony Liguori:
>
>> On 02/03/2010 08:11 AM, Natalia Portillo wrote:
>>> Indeed that section is just a static HTML so all the wiki advantages
>>> get lost with it.
>>
>> It's derived from qemu-doc.texi in the git tree so patches can be
>> submitted against it.
>>
>> I'd like to convert it to just a wiki page but there was quite a bit
>> of support for keeping it in the repository.
>
> Didn't that mostly apply to the ever-changing options,
> machine/hardware emulation etc.?
>
> Would there be something wrong with having the pretty stable
> ./configure --target-list=...; make; make install stuff in a new Wiki
> page and referencing the other stuff from there?
Nope. I think migrating chunks of reasonable static content from
qemu-doc.texi into the wiki would be a potentially non-contraversal
thing to do.
Regards,
Anthony Liguori
> Andreas
next prev parent reply other threads:[~2010-02-03 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 16:22 [Qemu-devel] The new qemu.org G 3
2010-02-03 8:07 ` Jes Sorensen
2010-02-03 14:11 ` Natalia Portillo
2010-02-03 14:15 ` Anthony Liguori
2010-02-03 19:20 ` Andreas Färber
2010-02-03 19:27 ` Anthony Liguori [this message]
2010-02-03 21:07 ` Natalia Portillo
[not found] <4b699711.1967f10a.2c22.ffff9768SMTPIN_ADDED@mx.google.com>
2010-02-03 17:00 ` G 3
2010-02-03 17:11 ` Anthony Liguori
2010-02-03 18:53 ` Andreas Färber
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=4B69CE26.6010609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Jes.Sorensen@redhat.com \
--cc=andreas.faerber@web.de \
--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).