From: Dave Jones <davej@suse.de>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org,
Guillaume Boissiere <boissiere@adiglobal.com>,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: bug database/webpage
Date: Mon, 22 Jul 2002 23:31:19 +0200 [thread overview]
Message-ID: <20020722233119.R27749@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0207221547360.19736-100000@dad.molina>; from tmolina@cox.net on Mon, Jul 22, 2002 at 03:59:01PM -0500
On Mon, Jul 22, 2002 at 03:59:01PM -0500, Thomas Molina wrote:
>
> In a conversation with Guillaume Boissiere it was mentioned that setting
> up a bug/problem report database for later in the 2.5 development cycle.
> Cox won't let me run an Apache web server from home with a bugzilla-type
> database (my preference), but I have been playing around with a simplistic
> web page problem report tracking available at
> http://members.cox.net/tmolina
>
> Would something like this be sufficient, or would a full-fledged server be
> required? Feedback/comments are welcome
Quite nice. It's a more organised version of what I had, but as the
number of reports gets higher and higher, it could end up being as much a
maintainence nightmare as the log I was updating.
Talking with a few folks about this problem at the summit, a few times
jitterbug was mentioned. My faded memory doesn't recall too much about
those days, but ultimatly it didn't work out.
I'm wondering how such a system would work out today.
There's even possibilites for neat things like checking
bitkeeper to automatically update status when Linus applies
a patch, which before required interaction from Linus.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-07-23 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 20:59 bug database/webpage Thomas Molina
2002-07-22 21:20 ` Rik van Riel
2002-07-22 21:39 ` Adrian Bunk
2002-07-22 22:02 ` Guillaume Boissiere
2002-07-22 21:31 ` Dave Jones [this message]
2002-07-23 2:17 ` Larry McVoy
2002-07-22 21:52 ` Jose Luis Domingo Lopez
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=20020722233119.R27749@suse.de \
--to=davej@suse.de \
--cc=boissiere@adiglobal.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=tmolina@cox.net \
/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