From: G 3 <programmingkidx@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: documentation
Date: Mon, 11 May 2009 15:53:35 -0400 [thread overview]
Message-ID: <805dd60006bc438b1f5f980b7306adf0@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0905112104360.27348@pacific.mpi-cbg.de>
On May 11, 2009, at 3:07 PM, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 11 May 2009, G 3 wrote:
>
>> I have been trying to compile Qemu on MinGW but I keep running into
>> problems. The biggest problem I face is outdated documentation. Who is
>> in charge of Qemu's documentation? In the section about compiling
>> under
>> Windows there is mention of a file called i386-mingw32msvb.tar.gz.
>> This
>> file doesn't exist any more in SDL 1.2.13.
>
> Well, nobody is in charge. This is an Open Source project, so people
> do
> what they like, and apparently nobody liked taking care of the
> documentation.
>
>> It would really help the Qemu community if they tried to update their
>> documentation.
>
> I fail to see how. The developers seemed to be quite capable of doing
> without the outdated documentation...
>
> Oh, and if you wanted to suggest that better documentation could give
> QEmu
> a bigger user community: as far as I can tell, nobody working on QEmu
> would have any benefit from a larger user base.
Better documentation would make it easier for users to actually make
Qemu. I know all you Qemu experts know how to compile the program, but
remember there are still people out there that don't know as much as
you do. It is only logical that up to date documentation be provided so
others may enjoy this program as well.
next prev parent reply other threads:[~2009-05-11 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 18:41 [Qemu-devel] documentation G 3
2009-05-11 19:07 ` Johannes Schindelin
2009-05-11 19:53 ` G 3 [this message]
2009-05-11 20:12 ` [Qemu-devel] documentation Gabriel Southern
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=805dd60006bc438b1f5f980b7306adf0@gmail.com \
--to=programmingkidx@gmail.com \
--cc=Johannes.Schindelin@gmx.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).