From: Rik van Riel <riel@conectiva.com.br>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Yay, bug tracking! (was Re: Bug tracking in the run up from 2.5 to 2.6)
Date: Mon, 21 Oct 2002 23:40:31 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.44L.0210212339190.22993-100000@imladris.surriel.com> (raw)
In-Reply-To: <3DB4A51E.3040405@pobox.com>
On Mon, 21 Oct 2002, Jeff Garzik wrote:
> Martin J. Bligh wrote:
> > We're proposing to create a bug tracking system to help keep track of
> > 2.5 kernel bugs ... in an attempt to help get 2.5 stabilised as quickly as
> > possible.
>
> This is fantastic.
<AOL/>
Count me in as a participant. One thing that would be nice is
a mailing list where the bugs (and the changes to bugs) get
mailed, so we can get updates by email.
I'll help track down, fix and admin bugs.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
Current spamtrap: <a href=mailto:"october@surriel.com">october@surriel.com</a>
next prev parent reply other threads:[~2002-10-22 1:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 22:52 Bug tracking in the run up from 2.5 to 2.6 Martin J. Bligh
2002-10-17 23:02 ` Timothy D. Witham
2002-10-18 13:41 ` mgross
2002-10-17 23:15 ` Greg KH
2002-10-17 23:47 ` Martin J. Bligh
2002-10-17 23:52 ` Zwane Mwaikambo
2002-10-18 0:08 ` Martin J. Bligh
2002-10-20 15:34 ` Arnaldo Carvalho de Melo
2002-10-19 12:48 ` Adrian Bunk
2002-10-20 15:22 ` Martin J. Bligh
2002-10-22 1:08 ` Yay, bug tracking! (was Re: Bug tracking in the run up from 2.5 to 2.6) Jeff Garzik
2002-10-22 1:40 ` Rik van Riel [this message]
2002-10-22 1:43 ` Martin J. Bligh
2002-10-22 9:49 ` Alan Cox
2002-10-22 9:37 ` Jeff Garzik
2002-10-24 18:34 ` Cliff White
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=Pine.LNX.4.44L.0210212339190.22993-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=Martin.Bligh@us.ibm.com \
--cc=jgarzik@pobox.com \
--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 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.