From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=43293 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OFY9U-00072z-2Y
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:45:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <anthony@codemonkey.ws>) id 1OFY9S-0007Hz-Dl
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:44:59 -0400
Received: from mail-vw0-f45.google.com ([209.85.212.45]:57926)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <anthony@codemonkey.ws>) id 1OFY9S-0007Ht-8Y
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:44:58 -0400
Received: by vws1 with SMTP id 1so1144073vws.4
	for <qemu-devel@nongnu.org>; Fri, 21 May 2010 12:44:55 -0700 (PDT)
Message-ID: <4BF6E2AE.6000106@codemonkey.ws>
Date: Fri, 21 May 2010 14:44:46 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [Bug 453617] Re: kvm hangs at 100% cpu when
	connecting
	to forwarded ports (when listed incorrectly on the command line)
References: <20091017002811.3816.18618.malonedeb@gangotri.canonical.com>
	<20100521115544.17238.22413.launchpad@loganberry.canonical.com>
	<20100521154252.GA12462@redhat.com> <4BF6DDA1.90304@codemonkey.ws>
	<20100521193700.GB27526@redhat.com>
In-Reply-To: <20100521193700.GB27526@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>

On 05/21/2010 02:37 PM, Gleb Natapov wrote:
> Another thing. If my memory serves me right it was promised that message
> will contain enough info to contact bug reporter without going through
> launchpad web interface. In other words email of bug reporter will be
> specified. I can't find it in the message.
>    

It is when the bug is original filed against the upstream project.

I think what you're suggesting is that bugs filed against a distro (say 
Ubuntu) should not just be marked as "also affects upstream" but rather 
that a new upstream bug should be filed.  It's still possible to connect 
the two bugs and I think it's not an unreasonable suggestion.

Regards,

Anthony Liguori

> --
> 			Gleb.
>