From: Dave Jones <davej@redhat.com>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Jens Axboe <axboe@suse.de>, Andrew Morton <akpm@osdl.org>,
James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: kernel bugzilla
Date: Sat, 18 Jun 2005 15:13:41 -0400 [thread overview]
Message-ID: <20050618191341.GA30620@redhat.com> (raw)
In-Reply-To: <491950000.1119044739@flay>
On Fri, Jun 17, 2005 at 02:45:39PM -0700, Martin J. Bligh wrote:
> The external one is infintely simpler than the internal IBM one, and
> the distro ones. I *really, really* prefer to keep it that way. Having
> said that, it does have a few fields (eg version, and category/subcategory) that should be filled out properly, and that's not easy to do via email.
> For now, my intent is to allow bug filing via web only, and followup
> comments by email. If lots of people scream and curse at me, I'll
> reconsider I suppose.
Something that I'd *really* love to see is usage of other bugzillas
xml-rpc interfaces, so that for eg, if someone files a Fedora bug
where some driver blows up, and I think it doesn't look like
it's caused by any patch in our tree, I'd love to click a button
in rh-bugzilla and have the bug automatically be also filed
in bugme.osdl, with the various comments mirrored back to the
originating bugzilla.
One of the problems faced by bug-reporters sometimes is that with
the multitude of bugzillas out there, and no cooperation between
them all, they don't know where to file their bug.
"My sound driver blew up, where do I file a bug"
bugzilla.redhat.com? bugme.osdl.org ? (in fact, I think the ALSA
folks have their own bugzilla if memory serves correctly)
[This demonstrates the problem -- even _I_ don't know, and I get a fair
amount of alsa bug reports from end-users]
I've never actually looked into the xml-rpc implementation of bugzilla,
so my mental-image of how this stuff works may be grossly oversimplified,
but I've heard multiple folks claim this should be possible with some
scripting. I've also heard people asking for the opposite.
"This bugme.osdl bug is present in RHEL/SLES/etc.. file a bug using
xml-rpc in the various bugzillas so that it gets backported".
Dave
next prev parent reply other threads:[~2005-06-18 19:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050617001330.294950ac.akpm@osdl.org>
[not found] ` <1119016223.5049.3.camel@mulgrave>
[not found] ` <20050617142225.GO6957@suse.de>
2005-06-17 21:10 ` kernel bugzilla Andrew Morton
2005-06-17 21:23 ` Jens Axboe
2005-06-17 21:39 ` Andrew Morton
2005-06-18 14:50 ` Alexey Dobriyan
2005-06-18 18:23 ` Andrew Morton
2005-06-20 18:59 ` Alexey Dobriyan
2005-06-18 15:45 ` Adrian Bunk
2005-06-18 15:58 ` Martin J. Bligh
2005-06-17 21:45 ` Martin J. Bligh
2005-06-18 19:13 ` Dave Jones [this message]
2005-06-19 2:54 ` Kyle Moffett
2005-06-19 8:22 ` Dave Jones
2005-06-19 16:58 ` Kyle Moffett
2005-06-20 11:58 ` Takashi Iwai
2005-06-20 14:08 ` Martin J. Bligh
2005-06-18 1:14 ` Herbert Xu
2005-06-19 19:02 Kenneth Parrish
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 23:04 Andrew Morton
2003-05-13 21:55 ` Diego Calleja García
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=20050618191341.GA30620@redhat.com \
--to=davej@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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