From: Joseph Glanville <joseph.glanville@orionvm.com.au>
To: Gordan Bobic <gordan@bobich.net>
Cc: xen-users <xen-users@lists.xen.org>,
jacek burghardt <jaceksburghardt@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen forum
Date: Sun, 19 May 2013 09:36:11 -0700 [thread overview]
Message-ID: <CAOzFzEhNE6uFW8gF6KPNdcB-pi_CbphseG1YhbhFyZzsjs6MzA@mail.gmail.com> (raw)
In-Reply-To: <5198ECBA.1040408@bobich.net>
Personally I think a public bug/issue tracker would be great. At the
moment this is somewhat handled by the distros, Debian and Ubuntu
primarily but it would be nice if there was a canonical issue tracker.
On 19 May 2013 08:16, Gordan Bobic <gordan@bobich.net> wrote:
> If the purpose of this is to raise visibility of bugs, a public bugzilla or
> similar would probably be a lot more useful than a forum.
>
> Gordan
>
>
> On 05/19/2013 04:09 PM, jacek burghardt wrote:
>>
>> I believe both mailing lists are great but there are so may postings
>> that many issues get missed. There are some bugs that hand never been
>> resolved because developers are unaware of it. I just setup forum for
>> xen users at sam.hebe.us/forums <http://sam.hebe.us/forums> please be
>> free to join
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
--
CTO | Orion Virtualisation Solutions | www.orionvm.com.au
Phone: 1300 56 99 52 | Mobile: 0428 754 846
next prev parent reply other threads:[~2013-05-19 16:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 15:09 xen forum jacek burghardt
2013-05-19 15:16 ` Gordan Bobic
2013-05-19 16:36 ` Joseph Glanville [this message]
2013-05-19 17:04 ` Gordan Bobic
2013-05-21 14:29 ` Konrad Rzeszutek Wilk
2013-05-21 14:57 ` Gordan Bobic
2013-05-21 15:04 ` [Xen-users] " Ian Campbell
2013-05-22 6:18 ` Bartek Krawczyk
[not found] ` <CAFp_H4vqFyNN-ZPTo-C2rN6_j1DsXWWPugNM8du9Ssa+V1FHAQ@mail.gmail.com>
2013-05-22 6:55 ` Gordan Bobic
2013-05-22 9:53 ` Ian Campbell
2013-05-22 9:58 ` George Dunlap
2013-05-22 15:27 ` Gordan Bobic
2013-05-22 15:32 ` George Dunlap
2013-05-22 15:52 ` Gordan Bobic
2013-05-22 15:53 ` Ian Campbell
2013-05-22 15:58 ` George Dunlap
2013-05-22 20:54 ` Gordan Bobic
2013-05-23 10:41 ` George Dunlap
2013-05-23 12:04 ` Ian Campbell
2013-05-23 13:08 ` George Dunlap
2013-05-22 10:20 ` George Dunlap
2013-05-22 15:24 ` Gordan Bobic
2013-05-22 16:18 ` George Dunlap
2013-05-22 16:44 ` Gordan Bobic
2013-05-23 13:40 ` George Dunlap
2013-05-21 15:04 ` Ian Murray
2013-05-21 15:19 ` Ian Campbell
2013-05-21 16:00 ` Ian Murray
2013-05-21 16:15 ` Ian Campbell
2013-05-21 17:57 ` Ian
2013-05-21 16:31 ` Konrad Rzeszutek Wilk
2013-05-21 17:19 ` jacek burghardt
2013-05-21 18:03 ` Ian
2013-05-24 14:04 ` Konrad Rzeszutek Wilk
2013-05-24 19:37 ` Gordan Bobic
2013-05-24 21:36 ` Stefano Stabellini
2013-05-24 22:14 ` Gordan Bobic
2013-05-25 12:06 ` Konrad Rzeszutek Wilk
2013-05-28 16:00 ` George Dunlap
2013-05-25 3:07 ` Andrew Bobulsky
2013-05-28 13:49 ` Konrad Rzeszutek Wilk
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=CAOzFzEhNE6uFW8gF6KPNdcB-pi_CbphseG1YhbhFyZzsjs6MzA@mail.gmail.com \
--to=joseph.glanville@orionvm.com.au \
--cc=gordan@bobich.net \
--cc=jaceksburghardt@gmail.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.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).