From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Maintainers master list?
Date: Fri, 22 Jun 2001 16:19:57 -0500 [thread overview]
Message-ID: <Ag1ABB.A.1QG._Z7M7@dinero.interactivesi.com> (raw)
In-Reply-To: <20010622170945.A16757@thyrsus.com>
In-Reply-To: <20010622160002.B16285@thyrsus.com> <Pine.LNX.4.33L.0106221753140.4442-100000@duckman.distro.conectiva> <Pine.LNX.4.33L.0106221753140.4442-100000@duckman.distro.conectiva> ; from riel@conectiva.com.br on Fri, Jun 22, 2001 at 05:54:20PM -0300
** Reply to message from "Eric S. Raymond" <esr@thyrsus.com> on Fri, 22 Jun
2001 17:09:45 -0400
> What happens now when somebody takes over responsibility for a file
> or subsystem and the MAINTAINERS file doesn't get patched, either because
> that person forgets to send a MAINTAINERS update or Linus doesn't
> happen to take the MAINTAINERS patch for a while?
Wouldn't this whole problem go away if the kernel source were stored in a
master CVS repository? Maintainers would have write access to their respective
code, but only Linus and Alan would have delete access. Everyone else would
have read-only access.
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
next prev parent reply other threads:[~2001-06-22 21:20 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
2001-06-22 21:09 ` Eric S. Raymond
2001-06-22 21:19 ` Timur Tabi [this message]
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=Ag1ABB.A.1QG._Z7M7@dinero.interactivesi.com \
--to=ttabi@interactivesi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®