From: "Marc Brekoo" <m_brekoo@mailandnews.com>
To: "Robert Love" <rml@tech9.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Maintainers master list?
Date: Wed, 27 Jun 2001 01:10:59 +0200 [thread overview]
Message-ID: <019701c0fe98$382c8620$c405a33e@Brekoo> (raw)
In-Reply-To: <Pine.LNX.4.33L.0106261602380.23373-100000@duckman.distro.conectiva> <993588379.763.0.camel@phantasy>
On Tue, 26 Jun 2001, Robert Love wrote:
> me. I took issue with the MAINTAINERS file when Eric brought it up
> originally. However, I don't think drastic measures need to be taken.
> I have seen a lot of ideas, including Meta-data in the kernel source.
>
> What I think we need is the simple solution: find a maintainer for the
> file, cleanup the current cruft and misinformation, and then actively
> work to keep the file current. I am willing to be this maintainer.
>
> I am not a major "maintainer" in the kernel, but I have and do
> contribute. Thus I think this is a good task for me. I am willing and
> wanting to do this. Comments?
I've been waiting for an opportunity like this to join in, so I'd be very
happy to help you with this.
(This would be my first contribution to linux, please be gentle :-)
Regards,
Marc Brekoo
next prev parent reply other threads:[~2001-06-26 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 17:53 Maintainers master list? Holzrichter, Bruce
2001-06-26 19:03 ` Rik van Riel
2001-06-26 20:46 ` Robert Love
2001-06-26 23:10 ` Marc Brekoo [this message]
2001-06-27 15:12 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2001-06-27 15:15 Holzrichter, Bruce
2001-06-22 20:48 Holzrichter, Bruce
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
2001-06-22 21:09 ` Eric S. Raymond
2001-06-22 21:19 ` Timur Tabi
2001-06-23 17:39 ` Rob Landley
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='019701c0fe98$382c8620$c405a33e@Brekoo' \
--to=m_brekoo@mailandnews.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddog@linux.nl \
--cc=rml@tech9.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