From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Werner Almesberger <Werner.Almesberger@epfl.ch>
Cc: linux-kernel@vger.kernel.org, engler@csl.Stanford.EDU
Subject: Re: [ANNOUNCE] The Janitor Project
Date: Mon, 26 Mar 2001 14:34:45 -0300 [thread overview]
Message-ID: <20010326143445.A1383@conectiva.com.br> (raw)
In-Reply-To: <20010322215215.A1052@conectiva.com.br> <20010327104321.B3974@almesberger.net>
In-Reply-To: <20010327104321.B3974@almesberger.net>; from Werner.Almesberger@epfl.ch on Tue, Mar 27, 2001 at 10:43:21AM +0200
Em Tue, Mar 27, 2001 at 10:43:21AM +0200, Werner Almesberger escreveu:
> Arnaldo Carvalho de Melo wrote:
> > http://bazar.conectiva.com.br/~acme/TODO
>
> BTW, I don't know if you're already interacting, but it seems to me that
> there are a lot of things on your list that look as if the MC project at
> Stanford ("CHECKER") could provide automated tests for them.
Yup, there has been some interaction in the past and I suggest that the
Stanford CHECKER people be subscribed to the kernel-janitors list or the
other way around, so that we can work more closely.
One thing is to find error patterns, and this is being done by the janitor
team and by any other interested people, other point is to go thru the
kernel sources and see where the patterns appear, and here the CHECKER is a
very important player if not the most important, and the other is to fix
the problems found, where active maintainers should do the work, despite
the fact that some are supposedly maintained (listed in MAINTAINERS or in
the kernel sources) some aren't, there are even drivers listed as
maintained but the maintainers don't even have the hardware anymore, and
new maintainers should appear or the janitors should do the work.
- Arnaldo
prev parent reply other threads:[~2001-03-27 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 0:52 [ANNOUNCE] The Janitor Project Arnaldo Carvalho de Melo
2001-03-27 8:43 ` Werner Almesberger
2001-03-26 17:34 ` Arnaldo Carvalho de Melo [this message]
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=20010326143445.A1383@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=Werner.Almesberger@epfl.ch \
--cc=engler@csl.Stanford.EDU \
--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