From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Murray <murrayie@yahoo.co.uk>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] xen forum
Date: Tue, 21 May 2013 12:31:02 -0400 [thread overview]
Message-ID: <20130521163102.GB3669@phenom.dumpdata.com> (raw)
In-Reply-To: <1369148649.60268.YahooMailNeo@web171304.mail.ir2.yahoo.com>
On Tue, May 21, 2013 at 04:04:09PM +0100, Ian Murray wrote:
>
>
> >It would be easier for us if the bug reports and such were posted on xen-devel.
> >Please consult http://www.chiark.greenend.org.uk/~sgtatham/bugs.html when
> >doing it.
> >
>
>
> My own experience is that posts (at least from me) are regularly missed/ignored on the devel list, including a signed patch, so I personally think a bug tracker would be a better option. Bug trackers don't (or at least shouldn't :) ) forget or miss. That's they're raison d'etre. I honestly don't know how anyone can do business using this list, but that's just my humble opinion.
Did you also look in the MAINTAINERS file to make sure you copied the right
maintainer?
The reason for skipping the Bugzilla system is that it is soo out of date that
we don't use it anymore.
>
> As professional developer and application support bod myself, I wouldn't ask anybody to read that missive; I wouldn't get any bug reports ever!
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-05-21 16:31 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
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 [this message]
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=20130521163102.GB3669@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=murrayie@yahoo.co.uk \
--cc=xen-devel@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).