From: Paul Brook <paul@codesourcery.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
jyoung5@us.ibm.com, qemu-devel@nongnu.org,
Jocelyn Mayer <l_indien@magic.fr>
Subject: Re: [kvm-ppc-devel] [Qemu-devel] TCG code in qemu has broken PPC host support .... anyone working on this?
Date: Thu, 21 Feb 2008 22:23:03 +0000 [thread overview]
Message-ID: <200802212223.05387.paul@codesourcery.com> (raw)
In-Reply-To: <1203631897.21867.1.camel@basalt>
> I'm not really familiar with the qemu development process; is this
> usually how it works? People are free to break things and assume others
> will fix it?
Not really. However this is fairly exceptional circumstances. The gcc3
dependency means it's getting harder and harder to build qemu at all.
Paul
prev parent reply other threads:[~2008-02-21 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 19:43 [Qemu-devel] TCG code in qemu has broken PPC host support .... anyone working on this? Jerone Young
2008-02-21 20:27 ` Paul Brook
2008-02-21 22:11 ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-21 22:23 ` Paul Brook [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=200802212223.05387.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=l_indien@magic.fr \
--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).