From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: Usefulness of the bug tracker
Date: Thu, 6 Jan 2011 17:11:18 +0200 [thread overview]
Message-ID: <20110106151118.GA17230@redhat.com> (raw)
In-Reply-To: <AANLkTinXG2epNKYk0m=O0tZmQD_i1cy1GsOPjdEvYksP@mail.gmail.com>
On Thu, Jan 06, 2011 at 10:28:46AM +0000, Stefan Hajnoczi wrote:
> The real problem is that we're collecting bugs but not effectively
> investigating and fixing them. Can Launchpad send out automatic bug
> summary emails once every week/two weeks/month?
Launchpad is at least part of the problem. Users
find it without going through the wiki and
file Ubuntu/Debian specific bugs there.
A bugzilla on qemu.org or some such place would make people look at the
documentation to file, and preferably
would not be associated with a distro to avoid confusion.
--
MST
next prev parent reply other threads:[~2011-01-06 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 14:06 [Qemu-devel] Usefulness of the bug tracker Aurelien Jarno
2011-01-06 10:28 ` Stefan Hajnoczi
2011-01-06 10:31 ` Stefan Hajnoczi
2011-01-06 15:11 ` Michael S. Tsirkin [this message]
2011-01-07 7:15 ` [Qemu-devel] " Jes Sorensen
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=20110106151118.GA17230@redhat.com \
--to=mst@redhat.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).