projects / deliverable / binutils-gdb.git / blame
| Commit | Line | Data |
|---|---|---|
| 302ab118 DD |
1 | ========= Binutils Maintainers ========= |
| 2 | ||
| 3 | This is the list of individuals responsible for maintenance and update | |
| 4 | of the "binutils" module, which includes the bfd, binutils, include, | |
| 5 | gas, gprof, ld, and opcodes subdirectories. The home page for binutils | |
| 6 | is http://sourceware.cygnus.com/binutils/ and patches should be sent to | |
| 7 | binutils@sourceware.cygnus.com with "[patch]" as part of the subject. | |
| 8 | ||
| 9 | --------- Blanket Write Privs --------- | |
| 10 | ||
| 11 | Nick Clifton <nickc@redhat.com> (head maintainer) | |
| 12 | Richard Henderson <rth@redhat.com> | |
| 13 | Ian Taylor <ian@zembu.com> | |
| 14 | Jeff Law <law@redhat.com> | |
| 15 | Jim Wilson <wilson@redhat.com> | |
| 16 | DJ Delorie <dj@redhat.com> | |
| 17 | Alan Modra <alan@linuxcare.com.au> | |
| 68dcecab | 18 | Michael Meissner <meissner@redhat.com> |
| 302ab118 DD |
19 | |
| 20 | --------- Maintainers --------- | |
| 21 | ||
| 22 | Maintainers are individuals who are responsible for, and have permission | |
| 23 | to check in changes in, certain subsets of the code. Note that | |
| 24 | maintainers still need approval to check in changes outside of the | |
| 25 | immediate domain that they maintain. | |
| 26 | ||
| 27 | If there is no maintainer for a given domain then the responsibility | |
| 28 | falls to the head maintainer (above). If there are several maintainers | |
| 29 | for a given domain then responsibility falls to the first maintainer. | |
| 30 | The first maintainer is free to devolve that responsibility among the | |
| 31 | other maintainers. | |
| 32 | ||
| 33 | MIPS Ulf Carlsson <ulfc@calypso.engr.sgi.com> | |
| 34 | PPC Geoff Keating <geoffk@redhat.com> | |
| 35 | ix86 COFF,PE DJ Delorie <dj@redhat.com> | |
| 36 | ARM Nick Clifton <nickc@redhat.com> | |
| 37 | ||
| 38 | --------- Write After Approval --------- | |
| 39 | ||
| 40 | Individuals with "write after approval" have the ability to check in | |
| 41 | changes, but they must get approval for each change from someone in | |
| 42 | one of the above lists (blanket write or maintainers). | |
| 43 | ||
| 44 | [It's a huge list, folks. You know who you are. If you have the | |
| 45 | *ability* to do binutils checkins, you're in this group. Just remember | |
| 46 | to get approval before checking anything in.] |