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

21.05.2010 19:56, Avi Kivity wrote:
> 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).

Aha. That makes perfect sense now.  Thanks!

/mjt