From: Stefan Weil <weil@mail.berlios.de>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Canonical web qemu-doc.html location?
Date: Fri, 06 May 2011 07:11:38 +0200 [thread overview]
Message-ID: <4DC3830A.1020304@mail.berlios.de> (raw)
In-Reply-To: <4DC332DA.2050201@landley.net>
Am 06.05.2011 01:29, schrieb Rob Landley:
> The wiki's Documentation tab links to:
>
> http://qemu.weilnetz.de/qemu-doc.html
>
> But Google's first hit for qemu-doc.html is:
>
> http://wiki.qemu.org/download/qemu-doc.html
>
> Which exists but is not remotely the same file.
>
> Which is correct?
>
> Rob
Both were made from the official source code, so both are
correct in some way.
The version on my private QEMU site is newer, because I
update it often when I build new QEMU binaries for w32.
It is not canonical because I am not an official QEMU
maintainer.
Ideally, the version on qemu.org would be updated automatically.
This can only be done by a site administrator.
Regards,
Stefan W.
prev parent reply other threads:[~2011-05-06 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 23:29 [Qemu-devel] Cannonical web qemu-doc.html location? Rob Landley
2011-05-06 5:11 ` Stefan Weil [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=4DC3830A.1020304@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).