public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>, Jens Axboe <axboe@suse.de>,
	Andrew Morton <akpm@osdl.org>,
	James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: kernel bugzilla
Date: Sun, 19 Jun 2005 04:22:51 -0400	[thread overview]
Message-ID: <20050619082251.GA6483@redhat.com> (raw)
In-Reply-To: <265EC713-9745-484D-8FF0-1C8D5FFE94F1@mac.com>

On Sat, Jun 18, 2005 at 10:54:33PM -0400, Kyle Moffett wrote:
 > On Jun 18, 2005, at 15:13:41, Dave Jones wrote:
 > >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.
 > 
 > Another wishlist feature I've seen is to have a mailing list archiver
 > attached to bugzilla that receives and stores the last month worth of
 > emails on the list.  At any time someone can login and:
 
The volume of mail bugzilla-mail generates is obscene.
I've been on vacation for a week, and I have over a 1000
mails waiting for me from rh-bugzilla when I get back
to give you an indication.[*]

A month worth is just mammoth, and unless you have a lot
of spare time on your hands (or you have have a masochistic streak),
most of it will go unread, so I'm not sure such an archive
would be particularly useful.

I do have a bunch of scripts for rh-bugzilla that could probably
be adapted to osdl-bugme to obtain stats etc like
"show me how many bugs are in state x for kernel y", I'll
take a look at doing that soon.

		Dave

[*] Ok, rh-bugzilla gets a 'little' more than osdl-bugme does,
but that may not always be the case, especially if escalating
bugs to upstream becomes easier.


  reply	other threads:[~2005-06-19  8:23 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
2005-06-19  2:54             ` Kyle Moffett
2005-06-19  8:22               ` Dave Jones [this message]
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=20050619082251.GA6483@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 \
    --cc=mrmacman_g4@mac.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