* maintainership
@ 2001-10-11 14:26 Jim Blandy
2001-10-11 15:17 ` maintainership Andrew Cagney
0 siblings, 1 reply; 2+ messages in thread
From: Jim Blandy @ 2001-10-11 14:26 UTC (permalink / raw)
To: gdb
Andrew, this decision is up to you, but I'm willing to take over the
following areas of maintainership until David Taylor resurfaces. I
think I've submitted patches to all of these areas within the last
year.
Target/Architecture:
d30v --target=d30v-elf ,-Werror
Core: Generic components used by all of GDB
language support David Taylor taylor@redhat.com
expression eval David Taylor taylor@redhat.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: maintainership
2001-10-11 14:26 maintainership Jim Blandy
@ 2001-10-11 15:17 ` Andrew Cagney
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Cagney @ 2001-10-11 15:17 UTC (permalink / raw)
To: Jim Blandy; +Cc: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-10-11 15:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-11 14:26 maintainership Jim Blandy
2001-10-11 15:17 ` maintainership Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox