From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: maintainership
Date: Thu, 11 Oct 2001 15:17:00 -0000 [thread overview]
Message-ID: <3BC61A4C.4050401@cygnus.com> (raw)
In-Reply-To: <20011011212728.835DA5E9D8@zwingli.cygnus.com>
Jim,
There are several things I've in mind for maintainership.
First is to water down the requirements for targets that don't have a
maintainer. For instance, the HP platform. While no one is probably up
for being its maintainer (there is soooo much work to do on it) I think
anyone listed in the MAINTAINERS file should be given a fairly free hand
to making changes to it. After all if someone notices it doesn't work
they should be free to patch it up so that it kind of works.
The same can be applied to targets that do have maintainers but the
maintainer is clearly inactive (typically they are overloaded).
The other is with much of the core stuff. There are vast chunks of it
that really don't need a maintainer - any change will either be obvious
or will require consensus from a number of people.
Andrew
prev parent reply other threads:[~2001-10-11 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 14:26 maintainership Jim Blandy
2001-10-11 15:17 ` Andrew Cagney [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=3BC61A4C.4050401@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@cygnus.com \
/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