From: Avi Kivity <avi@redhat.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call minutes for May 18
Date: Wed, 19 May 2010 20:02:51 +0300 [thread overview]
Message-ID: <4BF419BB.7010804@redhat.com> (raw)
In-Reply-To: <20100518142925.GA21120@x200.localdomain>
On 05/18/2010 05:29 PM, Chris Wright wrote:
>
> sourceforge bug tracker...
> - sucks
> - unclear if there's active triage
> - anthony prefers the launchpad instance
>
Kernel bugs can go to bugzilla.kernel.org. Of course it isn't always
clear if a bug is a kernel or qemu bug. Recommend we ask users to post
to the list first, get some guidance, then the bug is either resolved or
we ask them to file a bug report. Should improve the experience for
users and developers.
> - alex likes the sf email to list, wuld be good to keep that feature
>
Pretty critical IMO. The little attention the tracker gets is entirely
due to the email.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Chris Wright <chrisw@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for May 18
Date: Wed, 19 May 2010 20:02:51 +0300 [thread overview]
Message-ID: <4BF419BB.7010804@redhat.com> (raw)
In-Reply-To: <20100518142925.GA21120@x200.localdomain>
On 05/18/2010 05:29 PM, Chris Wright wrote:
>
> sourceforge bug tracker...
> - sucks
> - unclear if there's active triage
> - anthony prefers the launchpad instance
>
Kernel bugs can go to bugzilla.kernel.org. Of course it isn't always
clear if a bug is a kernel or qemu bug. Recommend we ask users to post
to the list first, get some guidance, then the bug is either resolved or
we ask them to file a bug report. Should improve the experience for
users and developers.
> - alex likes the sf email to list, wuld be good to keep that feature
>
Pretty critical IMO. The little attention the tracker gets is entirely
due to the email.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-05-19 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:29 KVM call minutes for May 18 Chris Wright
2010-05-18 14:29 ` [Qemu-devel] " Chris Wright
2010-05-18 21:34 ` Brian Jackson
2010-05-18 21:34 ` [Qemu-devel] " Brian Jackson
2010-05-18 22:08 ` Anthony Liguori
2010-05-18 22:08 ` [Qemu-devel] " Anthony Liguori
2010-05-19 17:02 ` Avi Kivity [this message]
2010-05-19 17:02 ` Avi Kivity
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=4BF419BB.7010804@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.