From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Stefano Bonifazi <stefboombastic@email.it>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Problems executing qemu-ppc
Date: Mon, 20 Dec 2010 09:36:04 +0700 [thread overview]
Message-ID: <AANLkTinmwL8KHM_oEiiz=jz8arSibmNPRHWpQQ3YokFP@mail.gmail.com> (raw)
In-Reply-To: <ielphg$jp6$1@dough.gmane.org>
Hi Stefano :)
On Mon, Dec 20, 2010 at 03:22, Stefano Bonifazi <stefboombastic@email.it> wrote:
> As part of my project I am writing a good QEMU technical documentation, .. I
> want to insert also this in it someway.. Then if my teacher's policy allows
> it I'll make my documentation public..I am experiencing big difficulties due
> to the lack of good updated documentation.. it is a huge C project, and C is
> not as readable as OO projects.. moreover one needs so many notions about
> emulators and computer architectures that can't be taught at university ..
> maybe some document written by who had to learn everything for understanding
> QEMU can be useful for novices more than one written by those who master all
> those topics for whom everything is easy and not worth to be said ;)
The best I could say for now is: try to strip out all the
"confidential" information in your document and try to label it as
Creative Common licensed document, or any other kind of open license.
After that, by submitting it to qemu wiki or forum, you can let other
improve it...thus you're not alone :)
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2010-12-20 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 17:27 [Qemu-devel] Problems executing qemu-ppc Stefano Bonifazi
2010-12-18 20:29 ` [Qemu-devel] " Stefano Bonifazi
2010-12-19 14:19 ` Mulyadi Santosa
2010-12-19 15:38 ` Alexander Graf
2010-12-19 20:22 ` Stefano Bonifazi
2010-12-20 2:36 ` Mulyadi Santosa [this message]
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='AANLkTinmwL8KHM_oEiiz=jz8arSibmNPRHWpQQ3YokFP@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefboombastic@email.it \
/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).