From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Farkas Levente <lfarkas-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Discussion about the virtualization on CentOS
<centos-virt-IFYaIzF+flcdnm+yROfE0A@public.gmane.org>
Subject: Re: [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn't work
Date: Fri, 05 Oct 2007 13:41:20 +0200 [thread overview]
Message-ID: <470622E0.5080503@qumranet.com> (raw)
In-Reply-To: <470543AC.50901-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
Farkas Levente wrote:
> ps. anyway it's planed to be temporary or permanent to use a qemu fork
> for kvm and not try to propagate changes back to the upstream qemu?
>
The plan is to submit everything to upstream qemu.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-05 11:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 16:25 [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn't work SourceForge.net
[not found] ` <E1IdTWB-0003Uo-Dv-fsxqSYOXIJgGKePtCzJsP6QD96bmaF075NbjCUgZEJk@public.gmane.org>
2007-10-04 16:33 ` Farkas Levente
[not found] ` <470515DA.9080606-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-10-04 16:54 ` Gregory Haskins
[not found] ` <1191516896.5019.83.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-10-04 17:27 ` Farkas Levente
[not found] ` <47052269.80501-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-10-04 17:42 ` Gregory Haskins
[not found] ` <1191519749.5019.99.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-10-04 19:49 ` Farkas Levente
[not found] ` <470543AC.50901-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-10-04 20:39 ` Gregory Haskins
[not found] ` <1191530370.5019.108.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-10-07 21:20 ` [RFC] let kvm be compiled with gcc4 and prevent users to shoot themselves in the foot while doing so (was Re: [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn't work) Carlo Marcelo Arenas Belon
2007-10-07 22:18 ` Jim Paris
[not found] ` <20071007221827.GA25232-lSbMZ+N7itA@public.gmane.org>
2007-10-08 6:15 ` Carlo Marcelo Arenas Belon
2007-10-05 11:41 ` Avi Kivity [this message]
2007-10-05 16:54 ` [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn't work Bernhard Kaindl
2007-10-05 17:00 ` Anthony Liguori
2007-10-08 15:43 ` [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn'twork Itamar Heim
-- strict thread matches above, loose matches on Subject: below --
2008-05-26 17:20 [ kvm-Bugs-1807620 ] KVM's --disable-gcc-check doesn't work SourceForge.net
2008-05-27 3:40 SourceForge.net
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=470622E0.5080503@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=centos-virt-IFYaIzF+flcdnm+yROfE0A@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lfarkas-lWVWdrzSO4GHXe+LvDLADg@public.gmane.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