All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: Dave Jones <davej@suse.de>
Cc: Stewart Smith <stewart@softhome.net>,
	timothy.covell@ashavan.org, linux-kernel@vger.kernel.org
Subject: Re: RFC: Linux Bug Tracking & Feature Tracking DB
Date: Mon, 31 Dec 2001 14:27:18 -0500	[thread overview]
Message-ID: <3C30BC16.6070809@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0112300038040.1336-100000@Appserv.suse.de>

>
>
>The advantage email has over this are too numerous to list,
>but they start with the fact that lots of kernel developers are
>lazy[*]. 2-3 keypresses to archive a patch for looking at later/merging
>are about the level of involvement thats aimed for.
>Having to start a browser, go to the bugzilla site, log in, search/browse
>for bugs etc.. way too involved.
>
>Dave.
>
>[*] In the sense that if life can be made easier, it should be.
>

That's a bit of apples and oranges ;)

Starting a browser is equivalent to starting a mail client.  In some 
instances it's the same program.

Hitting 2-3 keypresses to archive an email...how do you manage that 
archive v.s. it being managed for you w/ bugzilla?

Logging into bugzilla can be automatic, searching for a bug across the 
archive is in my opinion much more easily done w/ a relational database 
than grepping several mbox files that collect hundreds of messages a 
day.  Not to mention that comments on each bug are localized to -that- 
bug.  All said and done there are a lot of pros and cons from the newbie 
v.s. the 'Linus' perspective.  I think there is at least one or two 
irate persons per week here that have been fighting to find a solution 
to their problem and someone finally speaks up "oh yeah, do this".

It really would be nice to have a reference database -somewhere- where 
we could find answers or even just suggestions about the myriad of 
problems related to the kernel and what the kernel touches.

David

[*] RDBMSs do make my life much easier



  parent reply	other threads:[~2001-12-31 19:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29  6:53 RFC: Linux Bug Tracking & Feature Tracking DB Timothy Covell
2001-12-29  7:20 ` Anuradha Ratnaweera
2001-12-29 18:55 ` Larry McVoy
2001-12-29 19:08   ` Edgar Toernig
2001-12-29 22:13     ` Daniel Phillips
2001-12-29 22:52       ` Edgar Toernig
2001-12-29 23:02         ` Larry McVoy
2001-12-29 23:29           ` Edgar Toernig
2001-12-29 23:45             ` Larry McVoy
2001-12-29 19:16   ` Timothy Covell
2001-12-29 23:32 ` Stewart Smith
2001-12-29 23:45   ` Dave Jones
2001-12-30  5:24     ` Stewart Smith
2001-12-30 12:12       ` Dave Jones
2001-12-31  0:42         ` Richard Gooch
2001-12-31  0:44           ` H. Peter Anvin
2001-12-31  0:47             ` Richard Gooch
2001-12-31  0:52               ` H. Peter Anvin
2001-12-31  1:16                 ` Richard Gooch
2001-12-31  4:58                   ` H. Peter Anvin
2001-12-31  5:07                     ` Richard Gooch
2001-12-31  0:47             ` Arnaldo Carvalho de Melo
2001-12-31  0:49             ` Dave Jones
2001-12-31 21:50             ` Rob Landley
2001-12-31 19:40         ` David Ford
2001-12-31 19:27     ` David Ford [this message]
2001-12-31 20:00       ` Dave Jones
2002-01-02  2:27         ` David Ford
2002-01-01  6:35       ` Horst von Brand
2002-01-02  2:46         ` David Ford

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=3C30BC16.6070809@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stewart@softhome.net \
    --cc=timothy.covell@ashavan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.