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