From: Lorenzo Fernando Bivens de la Fuente <lorenzobivens@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Updated qemu wiki guide
Date: Sat, 31 Mar 2007 10:45:43 -0600 [thread overview]
Message-ID: <200703311045.43534.lorenzobivens@gmail.com> (raw)
In-Reply-To: <20070331000949.2B0CF1C0215@ws1-1.us4.outblaze.com>
Hola
We should divide that qemu guide into sections. Several steps are not only
Windows related. We could make something like
- Installing qemu
+ Windows
+ Lunix
+ ...
- Setting up Networking
+ Windows
+ You know who in tuxedo...
+ ...
- Running qemu
What do you think?
I can help with the lunix thingies, there isn't much to say.
On the other hand, I don't know if there is a wiki format standard, but I
would suggest to add a "table of contents" to long guides/articles.
Cheers!
Have a nice weekend!
next prev parent reply other threads:[~2007-03-31 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 0:09 ramkromberg
[not found] ` <f11045270703310203h29ae4626p6db470a99347b79e@mail.gmail.com>
2007-03-31 9:14 ` Primus
2007-03-31 16:45 ` Lorenzo Fernando Bivens de la Fuente [this message]
2007-03-31 21:47 ramkromberg
2007-04-01 5:12 ` lucio
2007-04-01 6:15 ` Skip Tavakkolian
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=200703311045.43534.lorenzobivens@gmail.com \
--to=lorenzobivens@gmail.com \
--cc=9fans@cse.psu.edu \
/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).