From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] wiki.qemu.org
Date: Fri, 29 Jan 2010 14:53:18 -0600 [thread overview]
Message-ID: <4B634ABE.2020100@codemonkey.ws> (raw)
In-Reply-To: <959734E2-77CD-472D-8557-EB8AE88E8766@web.de>
On 01/29/2010 02:29 PM, Andreas Färber wrote:
> Hi,
>
> Am 29.01.2010 um 20:44 schrieb Anthony Liguori:
>
>> I need to figure out what to do with the current texi documentation.
>> I think it makes sense to move qemu-doc.texi to a wiki page and
>> remove it from the source repository. The other option would be to
>> link to it as an external page and keep it within revision control.
>
> The latter allows to have a stable version on the website and a
> development version inside the repository.
> Otherwise we would either document unavailable options or, if we
> don't, probably forget adding Wiki documentation after a release.
> Also, would you want to ship a snapshot of the Wiki page with the
> source tarballs?
If we have documentation on the website, I think it may be appropriate
to just include a man page in the source tarball and leave all of the
other documentation on the website.
I think our user manual is currently a bit difficult to read through and
is certainly out of date in a lot of places. My expectation is that
putting it on the wiki would result in it becoming quite a bit more
readable and quite a bit more up-to-date.
> The Wiki looks more pretty though. :)
Yeah, I like it too. The theme is the same as what's used on
wiki.mozilla.org.
Regards,
Anthony Liguori
> Regards,
> Andreas
next prev parent reply other threads:[~2010-01-29 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 19:44 [Qemu-devel] [RFC] wiki.qemu.org Anthony Liguori
2010-01-29 20:23 ` Scott Tsai
2010-01-29 20:29 ` Andreas Färber
2010-01-29 20:53 ` Anthony Liguori [this message]
2010-01-29 21:47 ` Stefan Weil
2010-01-29 22:35 ` Anthony Liguori
2010-02-25 13:50 ` Paul Brook
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=4B634ABE.2020100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 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.