public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>, KVM list <kvm@vger.kernel.org>
Subject: Re: Bug tracking?
Date: Fri, 21 May 2010 20:12:05 +0400	[thread overview]
Message-ID: <4BF6B0D5.3060703@msgid.tls.msk.ru> (raw)
In-Reply-To: <4BF6AD45.4090504@redhat.com>

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

      reply	other threads:[~2010-05-21 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 12:45 Bug tracking? Michael Tokarev
2010-05-21 15:50 ` Anthony Liguori
2010-05-21 15:56   ` Avi Kivity
2010-05-21 16:12     ` Michael Tokarev [this message]

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=4BF6B0D5.3060703@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.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