From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4172] Documentation for MIPS Magnum R4000 machine.
Date: Tue, 08 Apr 2008 19:47:43 +0200 [thread overview]
Message-ID: <47FBAFBF.10207@mail.berlios.de> (raw)
In-Reply-To: <E1Jj6pu-0004Cm-ES@cvs.savannah.gnu.org>
Aurelien Jarno schrieb:
> Revision: 4172
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4172
> Author: aurel32
> Date: 2008-04-08 05:57:37 +0000 (Tue, 08 Apr 2008)
>
> Log Message:
> -----------
> Documentation for MIPS Magnum R4000 machine.
>
> Modified Paths:
> --------------
> trunk/qemu-doc.texi
>
> Modified: trunk/qemu-doc.texi
> ===================================================================
> (Binary files differ)
Binary file? Why that?
Regards
Stefan
next prev parent reply other threads:[~2008-04-08 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 5:57 [Qemu-devel] [4172] Documentation for MIPS Magnum R4000 machine Aurelien Jarno
2008-04-08 17:47 ` Stefan Weil [this message]
2008-04-08 18:39 ` Aurelien Jarno
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=47FBAFBF.10207@mail.berlios.de \
--to=weil@mail.berlios.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).