From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu Trac?
Date: Mon, 26 Jan 2009 19:18:20 -0600 [thread overview]
Message-ID: <497E60DC.7010203@codemonkey.ws> (raw)
In-Reply-To: <BAY110-DAV117031A6C288582AC828CCB9CB0@phx.gbl>
C.W. Betts wrote:
> Is there a trac or something similar that keeps track of bug reports
> and feature requests?
No. KVM has a bug tracker. Each distro has bug trackers too. To be
completely honest, the distro bug trackers are probably the best place
to file bugs simply because they have people who's job it is to poke
upstream developers about particular bugs :-) Of course, that requires
reproducing with the distro packages.
In terms of feature requests, you can post to the mailing list, but a
patch (even one that doesn't work all that well) is going to get you
much further than a request.
Regards,
Anthony Liguori
>
>
>
next prev parent reply other threads:[~2009-01-27 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0FEFBD04-E78E-4ABB-BF0F-D6A68E24D285@hotmail.com>
2009-01-27 0:53 ` [Qemu-devel] Qemu Trac? C.W. Betts
2009-01-27 1:18 ` Anthony Liguori [this message]
2009-01-27 8:43 ` Mark McLoughlin
2009-01-27 14:41 ` Anthony Liguori
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=497E60DC.7010203@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).