From: Mehmet Ergun <mehmetaergun@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] documentation
Date: Sat, 17 Feb 2007 01:37:46 -0000 [thread overview]
Message-ID: <45D65C5E.70200@gmail.com> (raw)
hi,
I'm a new user and I found the documentation a little confusing. I was
wondering whether you are considering to work on the online
documentation, provide a few videos, explain the network commands a bit
more, and do a general overhaul of the documentation structure.
A few videos explaining the installation and running the software would
be really nice :)
May be a few tutorials on how to do some interesting stuff with qemu?
thanks a lot for this nice software.
PS. please CC me on your replies as I'm not subscribed to the list
next reply other threads:[~2007-02-17 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 1:37 Mehmet Ergun [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-11 18:41 [Qemu-devel] documentation G 3
2009-05-11 19:07 ` Johannes Schindelin
2011-10-27 16:27 [Qemu-devel] Documentation Donald Allen
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=45D65C5E.70200@gmail.com \
--to=mehmetaergun@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).