1 ========= Binutils Maintainers =========
3 This is the list of individuals responsible for maintenance and update
4 of the GNU Binary Utilities project. This includes the linker (ld),
5 the assembler (gas), the profiler (gprof), a whole suite of other
6 programs (binutils) and the libraries that they use (bfd and
7 opcodes). This project shares a common set of header files with the
8 GCC and GDB projects (include), so maintainership of those files is
9 shared amoungst the projects.
11 The home page for binutils is:
13 http://www.gnu.org/software/binutils/binutils.html
15 and patches should be sent to:
17 binutils@sourceware.org
19 with "[Patch]" as part of the subject line. Note - patches to the
20 top level config.guess and config.sub scripts should be sent to:
22 config-patches@gnu.org
24 and not to the binutils lists. Patches to the other top level
25 configure files (configure, configure.in, config-ml.in) should
26 be sent to the binutils lists, and copied to the gcc and gdb
27 lists as well (gcc-patches@gcc.gnu.org and
28 gdb-patches@sourceware.org).
30 --------- Blanket Write Privs ---------
32 The following people have permission to check patches into the
33 repository without obtaining approval first:
35 Nick Clifton <nickc@redhat.com> (head maintainer)
36 Ian Lance Taylor <ian@airs.com>
37 Jeff Law <law@redhat.com>
38 Jim Wilson <wilson@tuliptree.org>
39 DJ Delorie <dj@redhat.com>
40 Alan Modra <amodra@gmail.com>
41 Michael Meissner <gnu@the-meissners.org>
42 Daniel Jacobowitz <drow@false.org>
43 Richard Sandiford <rdsandiford@googlemail.com>
45 --------- Maintainers ---------
47 Maintainers are individuals who are responsible for, and have
48 permission to check in changes in, certain subsets of the code. Note
49 that maintainers still need approval to check in changes outside of
50 the immediate domain that they maintain.
52 If there is no maintainer for a given domain then the responsibility
53 falls to the head maintainer (above). If there are several
54 maintainers for a given domain then responsibility falls to the first
55 maintainer. The first maintainer is free to devolve that
56 responsibility among the other maintainers.
58 ALPHA Richard Henderson <rth@twiddle.net>
59 AARCH64 Richard Earnshaw <rearnsha@arm.com>
60 AARCH64 Marcus Shawcroft <marcus.shawcroft@arm.com>
61 ARM Nick Clifton <nickc@redhat.com>
62 ARM Richard Earnshaw <rearnsha@arm.com>
63 ARM Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
64 AVR Denis Chertykov <chertykov@gmail.com>
65 AVR Marek Michalkiewicz <marekm@amelek.gda.pl>
66 BFIN Jie Zhang <jzhang918@gmail.com>
67 BFIN Mike Frysinger <vapier@gentoo.org>
68 BUILD SYSTEM Daniel Jacobowitz <drow@false.org>
69 CR16 M R Swami Reddy <MR.Swami.Reddy@nsc.com>
70 CRIS Hans-Peter Nilsson <hp@axis.com>
71 CRX M R Swami Reddy <MR.Swami.Reddy@nsc.com>
72 DLX Nikolaos Kavvadias <nkavv@physics.auth.gr>
73 DWARF2 Jason Merrill <jason@redhat.com>
74 DWARF2 Jakub Jelinek <jakub@redhat.com>
75 EPIPHANY Joern Rennecke <joern.rennecke@embecosm.com>
76 FR30 Dave Brolley <brolley@redhat.com>
77 FRV Dave Brolley <brolley@redhat.com>
78 FRV Alexandre Oliva <aoliva@redhat.com>
79 GOLD Ian Lance Taylor <iant@google.com>
80 GOLD Cary Coutant <ccoutant@gmail.com>
81 H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com>
82 HPPA Dave Anglin <dave.anglin@nrc.ca>
83 HPPA elf32 Alan Modra <amodra@gmail.com>
84 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only]
85 IA-64 Jim Wilson <wilson@tuliptree.org>
86 IQ2000 Stan Cox <scox@redhat.com>
87 i860 Jason Eckhardt <jle@rice.edu>
88 ix86 H.J. Lu <hjl.tools@gmail.com>
89 ix86 PE Christopher Faylor <me+binutils@cgf.cx>
90 ix86 COFF DJ Delorie <dj@redhat.com>
91 ix86 PE/COFF Dave Korn <dave.korn.cygwin@gmail.com>
92 ix86 INTEL MODE Jan Beulich <jbeulich@novell.com>
93 LM32 Jon Beniston <jon@beniston.com>
94 M32R Doug Evans <dje@sebabeach.org>
95 M68HC11 M68HC12 Stephane Carrez <Stephane.Carrez@gmail.com>
96 M68HC11 M68HC12 Sean Keys <skeys@ipdatasys.com>
97 M88k Mark Kettenis <kettenis@gnu.org>
98 MACH-O Tristan Gingold <tgingold@free.fr>
99 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com>
100 MEP Dave Brolley <brolley@redhat.com>
101 METAG Markos Chandras <markos.chandras@imgtec.com>
102 MICROBLAZE Michael Eager <eager@eagercon.com>
103 MIPS Maciej W. Rozycki <macro@imgtec.com>
104 MMIX Hans-Peter Nilsson <hp@bitrange.com>
105 MN10300 Alexandre Oliva <aoliva@redhat.com>
106 Moxie Anthony Green <green@moxielogic.com>
107 MSP430 Dmitry Diky <diwil@spec.ru>
108 NDS32 Kuan-Lin Chen <kuanlinchentw@gmail.com>
109 NDS32 Wei-Cheng Wang <cole945@gmail.com>
110 NetBSD support Matt Thomas <matt@netbsd.org>
111 Nios II Sandra Loosemore <sandra@codesourcery.com>
112 Nios II Andrew Jenner <andrew@codesourcery.com>
113 OR1K Christian Svensson <blue@cmd.nu>
114 OR1K Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
115 PPC Geoff Keating <geoffk@geoffk.org>
116 PPC Alan Modra <amodra@gmail.com>
117 PPC Peter Bergner <bergner@vnet.ibm.com>
118 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
119 RISC-V Palmer Dabbelt <palmer@dabbelt.com>
120 RISC-V Andrew Waterman <andrew@sifive.com>
121 RL78 DJ Delorie <dj@redhat.com>
122 RX DJ Delorie <dj@redhat.com>
123 RX Nick Clifton <nickc@redhat.com>
124 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
125 s390, s390x Andreas Krebbel <krebbel@linux.vnet.ibm.com>
126 SH Alexandre Oliva <aoliva@redhat.com>
127 SPARC David S. Miller <davem@davemloft.net>
128 SPARC Jose E. Marchesi <jose.marchesi@oracle.com>
129 SPU Alan Modra <amodra@gmail.com>
130 TIC4X Svein Seldal <svein@dev.seldal.com>
131 TIC54X Timothy Wall <twall@alum.mit.edu>
132 TIC6X Joseph Myers <joseph@codesourcery.com>
133 TILE-Gx Walter Lee <walt@tilera.com>
134 TILEPro Walter Lee <walt@tilera.com>
135 VAX Matt Thomas <matt@netbsd.org>
136 VAX Jan-Benedict Glaw <jbglaw@lug-owl.de>
137 VMS Tristan Gingold <tgingold@free.fr>
138 x86_64 Jan Hubicka <jh@suse.cz>
139 x86_64 Andreas Jaeger <aj@suse.de>
140 x86_64 H.J. Lu <hjl.tools@gmail.com>
141 XCOFF Richard Sandiford <r.sandiford@uk.ibm.com>
142 XGATE Sean Keys <skeys@ipdatasys.com>
143 Xtensa Sterling Augustine <augustine.sterling@gmail.com>
144 z80 Arnold Metselaar <arnold.metselaar@planet.nl>
145 z8k Christian Groessler <chris@groessler.org>
147 --------- Past Maintainers -------------
149 These folks have acted as maintainers in the past, but have now
150 moved on to other things. Our thanks for all their hard work
159 --------- CGEN Maintainers -------------
161 CGEN is a tool for building, amongst other things, assemblers,
162 disassemblers and simulators from a single description of a CPU.
163 It creates files in several of the binutils directories, but it
164 is mentioned here since there is a single group that maintains
165 CGEN and the files that it creates.
167 If you have CGEN related problems you can send email to;
171 The current CGEN maintainers are:
173 Doug Evans, Frank Eigler
175 --------- Write After Approval ---------
177 Individuals with "write after approval" have the ability to check in
178 changes, but they must get approval for each change from someone in
179 one of the above lists (blanket write or maintainers).
181 [It's a huge list, folks. You know who you are. If you have the
182 *ability* to do binutils checkins, you're in this group. Just
183 remember to get approval before checking anything in.]
185 ------------- Obvious Fixes -------------
187 Fixes for obvious mistakes do not need approval, and can be checked in
188 right away, but the patch should still be sent to the binutils list.
189 The definition of obvious is a bit hazy, and if you are not sure, then
190 you should seek approval first. Obvious fixes include fixes for
191 spelling mistakes, blatantly incorrect code (where the correct code is
192 also blatantly obvious), and so on. Obvious fixes should always be
193 small, the larger they are, the more likely it is that they contain
194 some un-obvious side effect or consequence.
196 --------- Branch Checkins ---------
198 If a patch is approved for check in to the mainline sources, it can
199 also be checked into the current release branch. Normally however
200 only bug fixes should be applied to the branch. New features, new
201 ports, etc, should be restricted to the mainline. (Otherwise the
202 burden of maintaining the branch in sync with the mainline becomes too
203 great). If you are uncertain as to whether a patch is appropriate for
204 the branch, ask the branch maintainer. This is:
206 (cf global maintainers)
208 -------- Testsuites ---------------
210 In general patches to any of the binutils testsuites should be
211 considered generic and sent to the binutils mailing list for
212 approval. Patches to target specific tests are the responsibility the
213 relevant port maintainer(s), and can be approved/checked in by them.
214 Other testsuite patches need the approval of a blanket-write-priveleges
217 -------- Configure patches ----------
219 Patches to the top level configure files (config.sub & config.guess)
220 are not the domain of the binutils project and they cannot be approved
221 by the binutils group. Instead they should be submitted to the config
224 config-patches@gnu.org
226 --------- Creating Branches ---------
228 Anyone with at least write-after-approval access may create a branch
229 to use for their own development purposes. In keeping with FSF
230 policies, all patches applied to such a branch must come from people
231 with appropriate copyright assignments on file. All legal
232 requirements that would apply to any other contribution apply equally
233 to contributions on a branch.
235 Before creating the branch, you should select a name for the branch of
238 binutils-<org>-<name>
240 where "org" is the initials of your organization, or your own initials
241 if you are acting as an individual. For example, for a branch created
242 by The GNUDist Company, "tgc" would be an appropriate choice for
243 "org". It's up to each organization to select an appropriate choice
244 for "name"; some organizations may use more structure than others, so
245 "name" may contain additional hyphens.
247 Suppose that The GNUDist Company was creating a branch to develop a
248 port of Binutils to the FullMonty processor. Then, an appropriate
249 choice of branch name would be:
253 A date stamp is not required as part of the name field, but some
254 organizations like to have one. If you do include the date, you
255 should follow these rules:
257 1. The date should be the date that the branch was created.
259 2. The date should be numerical and in the form YYYYMMDD.
263 binutils-tgc-fm_20050101
265 would be appropriate if the branch was created on January 1st, 2005.
267 Having selected the branch name, create the branch as follows:
269 1. Check out binutils, so that you have a git checkout corresponding
270 to the initial state of your branch.
274 git tag binutils-<org>-<name>-branchpoint
276 That tag will allow you, and others, to easily determine what's
277 changed on the branch relative to the initial state.
279 3. Create and push the branch:
281 git checkout -b binutils-<org>-<name>-branch
284 4. Document the branch:
286 Add a description of the branch to binutils/BRANCHES, and check
287 that file in. All branch descriptions should be added to the
288 HEAD revision of the file; it doesn't help to modify
289 binutils/BRANCHES on a branch!
291 Please do not commit any patches to a branch you did not create
292 without the explicit permission of the person who created the branch.
294 Copyright (C) 2012-2017 Free Software Foundation, Inc.
296 Copying and distribution of this file, with or without modification,
297 are permitted in any medium without royalty provided the copyright
298 notice and this notice are preserved.
projects / deliverable / binutils-gdb.git / blob