From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: Bug tracking?
Date: Fri, 21 May 2010 18:56:53 +0300
Message-ID: <4BF6AD45.4090504@redhat.com>
References: <4BF68063.2090004@msgid.tls.msk.ru> <4BF6ABC8.1050208@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Michael Tokarev <mjt@tls.msk.ru>, KVM list <kvm@vger.kernel.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:48185 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S933594Ab0EUP5G (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 21 May 2010 11:57:06 -0400
In-Reply-To: <4BF6ABC8.1050208@codemonkey.ws>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 05/21/2010 06:50 PM, Anthony Liguori wrote:
> On 05/21/2010 07:45 AM, Michael Tokarev wrote:
>> So, what's the current state of the bug tracking system?
>> As far as I can see, qemu is moving to launchpad.
>> Where qemu-kvm-related issues should be submitted nowadays?
>
> Kernel issues should be filed in bugzilla.kernel.org.
>
> qemu issues should be filed in LaunchPad.
>

qemu-kvm issues, even if not present in upstream qemu, should be filed 
in launchpad (but clearly marked to be qemu-kvm specific).

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.