public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Jens Axboe <axboe@suse.de>,
	James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: kernel bugzilla
Date: Sat, 18 Jun 2005 17:45:32 +0200	[thread overview]
Message-ID: <20050618154532.GR21393@stusta.de> (raw)
In-Reply-To: <20050617143946.00f387d0.akpm@osdl.org>

On Fri, Jun 17, 2005 at 02:39:46PM -0700, Andrew Morton wrote:
> Jens Axboe <axboe@suse.de> wrote:
> >
> > > One thing I haven't worked out is how to get a bug which is initially
> > > reported via email *into* the bugzilla system for tracking purposes.  One
> > > could just ask the originator to raise a bugzilla entry, as lots of other
> > > projects do.  But I don't think we want to do that - it's in our interest
> > > to make bug reporting as easy as possible for the reporter, rather than
> > > putting up barriers.
> > 
> > Depends... Sometimes it's quite ok to put the onus on the reported to
> > file it in bugzilla, since it should be considered in his best interest
> > to do so - he obviously filed the bug, because the issue bothers him in
> > some way. As long as it is 'easy enough' to do so, I think we are
> > alright. The question is if this can't be automated fairly easily. A
> > good bugzilla interface helps a _lot_.
> 
> Agree.  We should encourage people to use bugzilla as the initial
> entry-point.  But if someone instead uses email as the first contact I'm
> just a little bit reluctant to say "thanks, now go and try again".
> 
> Perhaps we could find some nice volunteer (hint) who could take the task of
> transferring such reports into bugzilla.  There wouldn't be very many, really.
>...

Why does this has to be done manually?

Reporting a bug in a Bugzilla only requires creating an account (if you 
don't have one) and entering the bug. It's not a "do it again", since 
the user already has the whole contents of the bug report. If you've 
written an email with a good bug report pasting it into a Bugzilla 
shouldn't be a problem.

The big problem for users of many bug tracking systems (including the 
kernel Bugzilla) is not that bug reporting was too hard. The problem is 
that bugs aren't handled in time.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2005-06-18 15:45 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 [this message]
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
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=20050618154532.GR21393@stusta.de \
    --to=bunk@stusta.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.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