From: "John R. Hogerhuis" <jhoger@speakeasy.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] .previous in exec-all.h
Date: Thu, 25 Mar 2004 16:43:51 -0800 [thread overview]
Message-ID: <1080261831.30846.2.camel@aragorn> (raw)
In-Reply-To: <1080207685.10208.23.camel@aragorn>
[-- Attachment #1: Type: text/plain, Size: 84 bytes --]
I fixed my problem, and was able to test today with this patch and it
works fine.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-26 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 18:26 [Qemu-devel] .previous in exec-all.h John R. Hogerhuis
2004-03-16 18:32 ` Mark IJbema
2004-03-19 18:34 ` Pierre d'Herbemont
2004-03-19 20:32 ` John R. Hogerhuis
2004-03-19 20:58 ` Fabrice Bellard
2004-03-19 21:10 ` John R. Hogerhuis
2004-03-25 9:41 ` John R. Hogerhuis
2004-03-26 0:43 ` John R. Hogerhuis [this message]
2004-03-19 21:03 ` [Qemu-devel] Win32 port [was: .previous in exec-all.h] Mike Nordell
2004-03-20 19:50 ` [Qemu-devel] .previous in exec-all.h Pierre d'Herbemont
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=1080261831.30846.2.camel@aragorn \
--to=jhoger@speakeasy.net \
--cc=jhoger@pobox.com \
--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).