From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p venti problem
Date: Thu, 11 Jun 2009 23:34:54 -0400 [thread overview]
Message-ID: <f75780240906112034k486932beoeeb0efc6cd4ddf1f@mail.gmail.com> (raw)
In-Reply-To: <3aaafc130906112000p2805a98ataaa4b2b32fdf8227@mail.gmail.com>
On Thu, Jun 11, 2009 at 11:00 PM, J.R. Mauro<jrm8005@gmail.com> wrote:
> I can't help with this in particular, but QEMU does some really
> low-level hackery to the point where it wouldn't compile with GCC 4,
> so it's possible something like that is going on here.
Thankfully, this is no longer true. QEMU 0.10 relies on completely
different low-level hackery...
-- vs
next prev parent reply other threads:[~2009-06-12 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 0:06 Adrian Tritschler
2009-06-12 3:00 ` J.R. Mauro
2009-06-12 3:34 ` Venkatesh Srinivas [this message]
2009-06-12 3:41 ` Venkatesh Srinivas
2009-06-12 6:55 ` Adrian Tritschler
2009-06-12 7:18 ` Venkatesh Srinivas
2009-06-12 7:26 ` Venkatesh Srinivas
2009-06-22 8:53 ` Mathieu
2009-06-12 14:07 ` J. R. Mauro
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=f75780240906112034k486932beoeeb0efc6cd4ddf1f@mail.gmail.com \
--to=me@acm.jhu.edu \
--cc=9fans@9fans.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).