From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>
Subject: Re: [Qemu-devel] [Bug 453617] Re: kvm hangs at 100% cpu when connecting to forwarded ports (when listed incorrectly on the command line)
Date: Fri, 21 May 2010 22:29:35 +0300 [thread overview]
Message-ID: <20100521192935.GA27526@redhat.com> (raw)
In-Reply-To: <4BF6DDA1.90304@codemonkey.ws>
On Fri, May 21, 2010 at 02:23:13PM -0500, Anthony Liguori wrote:
> On 05/21/2010 10:42 AM, Gleb Natapov wrote:
> >>ProblemType: Bug
> >>Architecture: amd64
> >>Date: Fri Oct 16 17:19:59 2009
> >>DistroRelease: Ubuntu 9.10
> >What is the point forwarding distro bugs here? Can we have upstream bug
> >tracker to report upstream issues?
>
> These bugs are being explicitly reported against upstream.
How should we know it from the message?
> Launchpad can also track status against distros bugs (Fedora,
> Debian, Gentoo, Ubuntu, etc.).
>
Great, here we only care about upstream.
> It can be annoying is if a very Ubuntu (or other distribution)
> specific bug report is marked also affects upstream without a clear
> indication that this was in fact explicitly tested against upstream
> (and what specific version was tested). This is something that we
> can fix though by just making protocol clear for this type of thing.
>
New bug should be opened against upstream. Then it will be crystal
clear that somebody took the time to check against upstream.
--
Gleb.
next prev parent reply other threads:[~2010-05-21 19:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091017002811.3816.18618.malonedeb@gangotri.canonical.com>
2010-05-21 11:55 ` [Qemu-devel] [Bug 453617] Re: kvm hangs at 100% cpu when connecting to forwarded ports (when listed incorrectly on the command line) Launchpad Bug Tracker
2010-05-21 15:42 ` Gleb Natapov
2010-05-21 16:31 ` Michael Tokarev
2010-05-21 17:16 ` [Qemu-devel] " Jan Kiszka
2010-05-21 17:22 ` Michael Tokarev
2010-05-21 17:29 ` Jan Kiszka
2010-05-21 18:12 ` Gleb Natapov
2010-05-21 17:23 ` Jan Kiszka
2010-05-21 18:07 ` [Qemu-devel] " Gleb Natapov
2010-05-21 19:23 ` Anthony Liguori
2010-05-21 19:29 ` Gleb Natapov [this message]
2010-05-21 19:37 ` Gleb Natapov
2010-05-21 19:44 ` Anthony Liguori
2010-05-21 19:48 ` Gleb Natapov
2016-11-07 18:20 ` Thomas Huth
2017-09-13 6:57 ` Thomas Huth
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=20100521192935.GA27526@redhat.com \
--to=gleb@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kirkland@canonical.com \
--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).