1 ========= Binutils Maintainers ========= 2 3This is the list of individuals responsible for maintenance and update 4of the GNU Binary Utilities project. This includes the linker (ld), 5the assembler (gas), the profiler (gprof), a whole suite of other 6programs (binutils) and the libraries that they use (bfd and 7opcodes). This project shares a common set of header files with the 8GCC and GDB projects (include), so maintainership of those files is 9shared amoungst the projects. 10 11The home page for binutils is: 12 13 http://www.gnu.org/software/binutils/binutils.html 14 15and patches should be sent to: 16 17 bug-binutils@gnu.org or binutils@sources.redhat.com 18 19with "[Patch]" as part of the subject line. Note - patches to the 20top level config.guess and config.sub scripts should be sent to: 21 22 config-patches@gnu.org 23 24and not to the binutils lists. Patches to the other top level 25configure files (configure, configure.in, config-ml.in) should 26be sent to the binutils lists, and copied to the gcc and gdb 27lists as well (gcc-patches@gcc.gnu.org and 28gdb-patches@sources.redhat.com). 29 30 --------- Blanket Write Privs --------- 31 32The following people have permission to check patches into the 33repository without obtaining approval first: 34 35 Nick Clifton <nickc@redhat.com> (head maintainer) 36 Richard Henderson <rth@redhat.com> 37 Ian Lance Taylor <ian@airs.com> 38 Jeff Law <law@redhat.com> 39 Jim Wilson <wilson@specifixinc.com> 40 DJ Delorie <dj@redhat.com> 41 Alan Modra <amodra@bigpond.net.au> 42 Michael Meissner <gnu@the-meissners.org> 43 Daniel Jacobowitz <dan@debian.org> 44 45 --------- Maintainers --------- 46 47Maintainers are individuals who are responsible for, and have 48permission to check in changes in, certain subsets of the code. Note 49that maintainers still need approval to check in changes outside of 50the immediate domain that they maintain. 51 52If there is no maintainer for a given domain then the responsibility 53falls to the head maintainer (above). If there are several 54maintainers for a given domain then responsibility falls to the first 55maintainer. The first maintainer is free to devolve that 56responsibility among the other maintainers. 57 58 ALPHA Richard Henderson <rth@redhat.com> 59 ARM Nick Clifton <nickc@redhat.com> 60 ARM Richard Earnshaw <rearnsha@arm.com> 61 ARM (Symbian) Paul Brook <paul@codesourcery.com> 62 ARM (Symbian) Mark Mitchell <mark@codesourcery.com> 63 AVR Denis Chertykov <denisc@overta.ru> 64 AVR Marek Michalkiewicz <marekm@amelek.gda.pl> 65 BFIN Jie Zhang <jie.zhang@analog.com> 66 BFIN Bernd Schmidt <bernd.schmidt@analog.com> 67 BUILD SYSTEM Ben Elliston <bje@gnu.org> 68 BUILD SYSTEM Daniel Jacobowitz <dan@debian.org> 69 CRIS Hans-Peter Nilsson <hp@axis.com> 70 CRX Tomer Levi <Tomer.Levi@nsc.com> 71 DLX Nikolaos Kavvadias <nkavv@physics.auth.gr> 72 DWARF2 Jason Merrill <jason@redhat.com> 73 FR30 Dave Brolley <brolley@redhat.com> 74 FRV Dave Brolley <brolley@redhat.com> 75 FRV Alexandre Oliva <aoliva@redhat.com> 76 H8300 Anil Paranjpe <anilp1@kpitcummins.com> 77 HPPA Dave Anglin <dave.anglin@nrc.ca> 78 HPPA elf32 Alan Modra <amodra@bigpond.net.au> 79 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only] 80 IA-64 Jim Wilson <wilson@specifixinc.com> 81 IQ2000 Stan Cox <scox@redhat.com> 82 i860 Jason Eckhardt <jle@rice.edu> 83 ix86 Alan Modra <amodra@bigpond.net.au> 84 ix86 PE Christopher Faylor <cgf@redhat.com> 85 ix86 COFF DJ Delorie <dj@redhat.com> 86 ix86 H.J. Lu <hjl@gnu.org> 87 ix86 INTEL MODE Jan Beulich <jbeulich@novell.com> 88 M68HC11 M68HC12 Stephane Carrez <stcarrez@nerim.fr> 89 M68k Ben Elliston <bje@gnu.org> 90 M88k Mark Kettenis <kettenis@gnu.org> 91 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com> 92 MEP Dave Brolley <brolley@redhat.com> 93 MIPS Eric Christopher <echristo@apple.com> 94 MIPS Thiemo Seufer <ths@networkno.de> 95 MMIX Hans-Peter Nilsson <hp@bitrange.com> 96 MN10300 Eric Christopher <echristo@apple.com> 97 MN10300 Alexandre Oliva <aoliva@redhat.com> 98 MSP430 Dmitry Diky <diwil@spec.ru> 99 PPC Geoff Keating <geoffk@geoffk.org> 100 PPC vector ext Aldy Hernandez <aldyh@redhat.com> 101 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com> 102 SCORE Mei Ligang <ligang@sunnorth.com.cn> 103 SH Alexandre Oliva <aoliva@redhat.com> 104 SH Kaz Kojima <kkojima@rr.iij4u.or.jp> 105 SPARC Jakub Jelinek <jakub@redhat.com> 106 TESTSUITES Ben Elliston <bje@gnu.org> 107 TIC4X Svein Seldal <svein@dev.seldal.com> 108 TIC54X Timothy Wall <twall@alum.mit.edu> 109 VAX Jason R Thorpe <thorpej@netbsd.org> 110 VAX Jan-Benedict Glaw <jbglaw@lug-owl.de> 111 x86_64 Jan Hubicka <jh@suse.cz> 112 x86_64 Andreas Jaeger <aj@suse.de> 113 x86_64 H.J. Lu <hjl@gnu.org> 114 Xtensa Bob Wilson <bob.wilson@acm.org> 115 z80 Arnold Metselaar <arnold.metselaar@planet.nl> 116 z8k Christian Groessler <chris@groessler.org> 117 118 119 --------- CGEN Maintainers ------------- 120 121CGEN is a tool for building, amongst other things, assemblers, 122disassemblers and simulators from a single description of a CPU. 123It creates files in several of the binutils directories, but it 124is mentioned here since there is a single group that maintains 125CGEN and the files that it creates. 126 127If you have CGEN related problems you can send email to; 128 129 cgen@sources.redhat.com 130 131The current CGEN maintainers are: 132 133 Doug Evans, Frank Eigler 134 135 --------- Write After Approval --------- 136 137Individuals with "write after approval" have the ability to check in 138changes, but they must get approval for each change from someone in 139one of the above lists (blanket write or maintainers). 140 141[It's a huge list, folks. You know who you are. If you have the 142 *ability* to do binutils checkins, you're in this group. Just 143 remember to get approval before checking anything in.] 144 145 ------------- Obvious Fixes ------------- 146 147Fixes for obvious mistakes do not need approval, and can be checked in 148right away, but the patch should still be sent to the binutils list. 149The definition of obvious is a bit hazy, and if you are not sure, then 150you should seek approval first. Obvious fixes include fixes for 151spelling mistakes, blatantly incorrect code (where the correct code is 152also blatantly obvious), and so on. Obvious fixes should always be 153small, the larger they are, the more likely it is that they contain 154some un-obvious side effect or consequence. 155 156 --------- Branch Checkins --------- 157 158If a patch is approved for check in to the mainline sources, it can 159also be checked into the current release branch. Normally however 160only bug fixes should be applied to the branch. New features, new 161ports, etc, should be restricted to the mainline. (Otherwise the 162burden of maintaining the branch in sync with the mainline becomes too 163great). If you are uncertain as to whether a patch is appropriate for 164the branch, ask the branch maintainer. This is: 165 166 Daniel Jacobowitz <dan@debian.org> 167 168 -------- Testsuites --------------- 169 170In general patches to any of the binutils testsuites should be 171considered generic and sent to the binutils mailing list for 172approval. Patches to target specific tests are the responsibility the 173relevent port maintainer(s), and can be approved/checked in by them. 174Other testsuite patches need the approval of a blanket-write-priveleges 175person. 176 177 -------- Configure patches ---------- 178 179Patches to the top level configure files (config.sub & config.guess) 180are not the domain of the binutils project and they cannot be approved 181by the binutils group. Instead they should be submitted to the config 182maintainer at: 183 184 config-patches@gnu.org 185 186 --------- Creating Branches --------- 187 188Anyone with at least write-after-approval access may create a branch 189to use for their own development purposes. In keeping with FSF 190policies, all patches applied to such a branch must come from people 191with appropriate copyright assignments on file. All legal 192requirements that would apply to any other contribution apply equally 193to contributions on a branch. 194 195Before creating the branch, you should select a name for the branch of 196the form: 197 198 binutils-<org>-<name> 199 200where "org" is the initials of your organization, or your own initials 201if you are acting as an individual. For example, for a branch created 202by The GNUDist Company, "tgc" would be an appropriate choice for 203"org". It's up to each organization to select an appropriate choice 204for "name"; some organizations may use more structure than others, so 205"name" may contain additional hyphens. 206 207Suppose that The GNUDist Company was creating a branch to develop a 208port of Binutils to the FullMonty processor. Then, an appropriate 209choice of branch name would be: 210 211 binutils-tgc-fm 212 213A data stamp is not required as part of the name field, but some 214organizations like to have one. If you do include the date, you 215should follow these rules: 216 2171. The date should be the date that the branch was created. 218 2192. The date should be numerical and in the form YYYYMMDD. 220 221For example: 222 223 binutils-tgc-fm_20050101 224 225would be appropriate if the branch was created on January 1st, 2005. 226 227Having selected the branch name, create the branch as follows: 228 2291. Check out binutils, so that you have a CVS checkout corresponding 230 to the initial state of your branch. 231 2322. Create a tag: 233 234 cvs tag binutils-<org>-<name>-branchpoint 235 236 That tag will allow you, and others, to easily determine what's 237 changed on the branch relative to the initial state. 238 2393. Create the branch: 240 241 cvs rtag -b -r binutils-<org>-<name>-branchpoint \ 242 binutils-<org>-<name>-branch 243 2444. Document the branch: 245 246 Add a description of the branch to binutils/BRANCHES, and check 247 that file in. All branch descriptions should be added to the 248 HEAD revision of the file; it doesn't help to modify 249 binutils/BRANCHES on a branch! 250 251Please do not commit any patches to a branch you did not create 252without the explicit permission of the person who created the branch. 253