From: Anthony Liguori <anthony@codemonkey.ws>
To: Gleb Natapov <gleb@redhat.com>
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 14:44:46 -0500 [thread overview]
Message-ID: <4BF6E2AE.6000106@codemonkey.ws> (raw)
In-Reply-To: <20100521193700.GB27526@redhat.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.
>
next prev parent reply other threads:[~2010-05-21 19:45 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
2010-05-21 19:37 ` Gleb Natapov
2010-05-21 19:44 ` Anthony Liguori [this message]
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=4BF6E2AE.6000106@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gleb@redhat.com \
--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).