From: "Hetz Ben Hamo" <hetzbh@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Thanks for QEMU!
Date: Tue, 7 Nov 2006 19:42:59 +0200 [thread overview]
Message-ID: <41e41e7a0611070942l622c95e7h2875f356b496f837@mail.gmail.com> (raw)
In-Reply-To: <1162912144.3332.32.camel@client-30.office.endeca.com>
Hi,
On 11/7/06, John Stracke <francis+dated+1178460433.897649@thibault.org> wrote:
> Just wanted to send a thank-you for developing QEMU. I'm writing an OS
> for my master's thesis, and having an open-source emulation of the CPU
> has been a *huge* help. At least three times now, there's been some
> subtlety that I couldn't figure out from the CPU docs, so I adding some
> printf()s to QEMU to figure out what was really going on.
Perhaps you could submit your printf's so other people can learn from
them please?
Thanks,
Hetz
next prev parent reply other threads:[~2006-11-07 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 15:09 [Qemu-devel] Thanks for QEMU! John Stracke
2006-11-07 17:42 ` Hetz Ben Hamo [this message]
2006-11-08 9:30 ` wangji
[not found] <200611081431.28389.hoan@wanadoo.fr>
2006-11-08 14:34 ` John Stracke
-- strict thread matches above, loose matches on Subject: below --
2006-11-08 14:44 John Stracke
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=41e41e7a0611070942l622c95e7h2875f356b496f837@mail.gmail.com \
--to=hetzbh@gmail.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).