From: Rik van Riel <riel@conectiva.com.br>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: "Holzrichter, Bruce" <bruce.holzrichter@monster.com>,
David Woodhouse <dwmw2@infradead.org>,
Russell King <rmk@arm.linux.org.uk>,
<linux-kernel@vger.kernel.org>,
<kbuild-devel@lists.sourceforge.net>
Subject: Re: Maintainers master list?
Date: Fri, 22 Jun 2001 17:54:20 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0106221753140.4442-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20010622160002.B16285@thyrsus.com>
On Fri, 22 Jun 2001, Eric S. Raymond wrote:
> I have proposed that the MAINTAINERS file should be replaced by
> metadata markup in the kernel sources themselves, distributed so that
> it will naturally be kept up to date by the people named in it and
> mechanically gathered into a generated MAINTAINERS at make dep time.
Look, when somebody stops maintaining something, they'll
stop sending patches. When this happens it's only natural
that the information you want to use to generate the
MAINTAINERS file is also out of date.
I fail to see how your idea would solve anything.
regards,
Rik
--
Executive summary of a recent Microsoft press release:
"we are concerned about the GNU General Public License (GPL)"
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com/
next prev parent reply other threads:[~2001-06-22 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 14:47 Missing help entries in 2.4.6pre5 Holzrichter, Bruce
2001-06-22 20:00 ` Maintainers master list? Eric S. Raymond
2001-06-22 20:54 ` Rik van Riel [this message]
2001-06-22 21:09 ` Eric S. Raymond
2001-06-22 21:19 ` Timur Tabi
2001-06-23 17:39 ` Rob Landley
2001-06-22 20:48 Holzrichter, Bruce
2001-06-26 17:53 Holzrichter, Bruce
2001-06-26 19:03 ` Rik van Riel
2001-06-26 20:46 ` Robert Love
2001-06-26 23:10 ` Marc Brekoo
2001-06-27 15:12 ` Jes Sorensen
2001-06-27 15:15 Holzrichter, Bruce
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.33L.0106221753140.4442-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=bruce.holzrichter@monster.com \
--cc=dwmw2@infradead.org \
--cc=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).