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 dwarf-mode.el Tom Tromey <tom@tromey.com>
76 EPIPHANY Joern Rennecke <joern.rennecke@embecosm.com>
77 FR30 Dave Brolley <brolley@redhat.com>
78 FRV Dave Brolley <brolley@redhat.com>
79 FRV Alexandre Oliva <aoliva@redhat.com>
80 GOLD Ian Lance Taylor <iant@google.com>
81 GOLD Cary Coutant <ccoutant@gmail.com>
82 H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com>
83 HPPA Dave Anglin <dave.anglin@nrc.ca>
84 HPPA elf32 Alan Modra <amodra@gmail.com>
85 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only]
86 IA-64 Jim Wilson <wilson@tuliptree.org>
87 IQ2000 Stan Cox <scox@redhat.com>
88 i860 Jason Eckhardt <jle@rice.edu>
89 ix86 H.J. Lu <hjl.tools@gmail.com>
90 ix86 PE Christopher Faylor <me+binutils@cgf.cx>
91 ix86 COFF DJ Delorie <dj@redhat.com>
92 ix86 PE/COFF Dave Korn <dave.korn.cygwin@gmail.com>
93 ix86 INTEL MODE Jan Beulich <jbeulich@novell.com>
94 LM32 Jon Beniston <jon@beniston.com>
95 M32R Doug Evans <dje@sebabeach.org>
96 M68HC11 M68HC12 Stephane Carrez <Stephane.Carrez@gmail.com>
97 M68HC11 M68HC12 Sean Keys <skeys@ipdatasys.com>
98 M88k Mark Kettenis <kettenis@gnu.org>
99 MACH-O Tristan Gingold <tgingold@free.fr>
100 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com>
101 MEP Dave Brolley <brolley@redhat.com>
102 METAG Markos Chandras <markos.chandras@imgtec.com>
103 MICROBLAZE Michael Eager <eager@eagercon.com>
104 MIPS Maciej W. Rozycki <macro@imgtec.com>
105 MMIX Hans-Peter Nilsson <hp@bitrange.com>
106 MN10300 Alexandre Oliva <aoliva@redhat.com>
107 Moxie Anthony Green <green@moxielogic.com>
108 MSP430 Dmitry Diky <diwil@spec.ru>
109 NDS32 Kuan-Lin Chen <kuanlinchentw@gmail.com>
110 NDS32 Wei-Cheng Wang <cole945@gmail.com>
111 NetBSD support Matt Thomas <matt@netbsd.org>
112 Nios II Sandra Loosemore <sandra@codesourcery.com>
113 Nios II Andrew Jenner <andrew@codesourcery.com>
114 OR1K Christian Svensson <blue@cmd.nu>
115 OR1K Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
116 PPC Geoff Keating <geoffk@geoffk.org>
117 PPC Alan Modra <amodra@gmail.com>
118 PPC Peter Bergner <bergner@vnet.ibm.com>
119 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
120 RISC-V Palmer Dabbelt <palmer@dabbelt.com>
121 RISC-V Andrew Waterman <andrew@sifive.com>
122 RL78 DJ Delorie <dj@redhat.com>
123 RX DJ Delorie <dj@redhat.com>
124 RX Nick Clifton <nickc@redhat.com>
125 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
126 s390, s390x Andreas Krebbel <krebbel@linux.vnet.ibm.com>
127 SH Alexandre Oliva <aoliva@redhat.com>
128 SPARC David S. Miller <davem@davemloft.net>
129 SPARC Jose E. Marchesi <jose.marchesi@oracle.com>
130 SPU Alan Modra <amodra@gmail.com>
131 TIC4X Svein Seldal <svein@dev.seldal.com>
132 TIC54X Timothy Wall <twall@alum.mit.edu>
133 TIC6X Joseph Myers <joseph@codesourcery.com>
134 TILE-Gx Walter Lee <walt@tilera.com>
135 TILEPro Walter Lee <walt@tilera.com>
136 VAX Matt Thomas <matt@netbsd.org>
137 VAX Jan-Benedict Glaw <jbglaw@lug-owl.de>
138 VMS Tristan Gingold <tgingold@free.fr>
139 x86_64 Jan Hubicka <jh@suse.cz>
140 x86_64 Andreas Jaeger <aj@suse.de>
141 x86_64 H.J. Lu <hjl.tools@gmail.com>
142 XCOFF Richard Sandiford <r.sandiford@uk.ibm.com>
143 XGATE Sean Keys <skeys@ipdatasys.com>
144 Xtensa Sterling Augustine <augustine.sterling@gmail.com>
145 z80 Arnold Metselaar <arnold.metselaar@planet.nl>
146 z8k Christian Groessler <chris@groessler.org>
148 --------- Past Maintainers -------------
150 These folks have acted as maintainers in the past, but have now
151 moved on to other things. Our thanks for all their hard work
160 --------- CGEN Maintainers -------------
162 CGEN is a tool for building, amongst other things, assemblers,
163 disassemblers and simulators from a single description of a CPU.
164 It creates files in several of the binutils directories, but it
165 is mentioned here since there is a single group that maintains
166 CGEN and the files that it creates.
168 If you have CGEN related problems you can send email to;
172 The current CGEN maintainers are:
174 Doug Evans, Frank Eigler
176 --------- Write After Approval ---------
178 Individuals with "write after approval" have the ability to check in
179 changes, but they must get approval for each change from someone in
180 one of the above lists (blanket write or maintainers).
182 [It's a huge list, folks. You know who you are. If you have the
183 *ability* to do binutils checkins, you're in this group. Just
184 remember to get approval before checking anything in.]
186 ------------- Obvious Fixes -------------
188 Fixes for obvious mistakes do not need approval, and can be checked in
189 right away, but the patch should still be sent to the binutils list.
190 The definition of obvious is a bit hazy, and if you are not sure, then
191 you should seek approval first. Obvious fixes include fixes for
192 spelling mistakes, blatantly incorrect code (where the correct code is
193 also blatantly obvious), and so on. Obvious fixes should always be
194 small, the larger they are, the more likely it is that they contain
195 some un-obvious side effect or consequence.
197 --------- Branch Checkins ---------
199 If a patch is approved for check in to the mainline sources, it can
200 also be checked into the current release branch. Normally however
201 only bug fixes should be applied to the branch. New features, new
202 ports, etc, should be restricted to the mainline. (Otherwise the
203 burden of maintaining the branch in sync with the mainline becomes too
204 great). If you are uncertain as to whether a patch is appropriate for
205 the branch, ask the branch maintainer. This is:
207 (cf global maintainers)
209 -------- Testsuites ---------------
211 In general patches to any of the binutils testsuites should be
212 considered generic and sent to the binutils mailing list for
213 approval. Patches to target specific tests are the responsibility the
214 relevant port maintainer(s), and can be approved/checked in by them.
215 Other testsuite patches need the approval of a blanket-write-priveleges
218 -------- Configure patches ----------
220 Patches to the top level configure files (config.sub & config.guess)
221 are not the domain of the binutils project and they cannot be approved
222 by the binutils group. Instead they should be submitted to the config
225 config-patches@gnu.org
227 --------- Creating Branches ---------
229 Anyone with at least write-after-approval access may create a branch
230 to use for their own development purposes. In keeping with FSF
231 policies, all patches applied to such a branch must come from people
232 with appropriate copyright assignments on file. All legal
233 requirements that would apply to any other contribution apply equally
234 to contributions on a branch.
236 Before creating the branch, you should select a name for the branch of
239 binutils-<org>-<name>
241 where "org" is the initials of your organization, or your own initials
242 if you are acting as an individual. For example, for a branch created
243 by The GNUDist Company, "tgc" would be an appropriate choice for
244 "org". It's up to each organization to select an appropriate choice
245 for "name"; some organizations may use more structure than others, so
246 "name" may contain additional hyphens.
248 Suppose that The GNUDist Company was creating a branch to develop a
249 port of Binutils to the FullMonty processor. Then, an appropriate
250 choice of branch name would be:
254 A date stamp is not required as part of the name field, but some
255 organizations like to have one. If you do include the date, you
256 should follow these rules:
258 1. The date should be the date that the branch was created.
260 2. The date should be numerical and in the form YYYYMMDD.
264 binutils-tgc-fm_20050101
266 would be appropriate if the branch was created on January 1st, 2005.
268 Having selected the branch name, create the branch as follows:
270 1. Check out binutils, so that you have a git checkout corresponding
271 to the initial state of your branch.
275 git tag binutils-<org>-<name>-branchpoint
277 That tag will allow you, and others, to easily determine what's
278 changed on the branch relative to the initial state.
280 3. Create and push the branch:
282 git checkout -b binutils-<org>-<name>-branch
285 4. Document the branch:
287 Add a description of the branch to binutils/BRANCHES, and check
288 that file in. All branch descriptions should be added to the
289 HEAD revision of the file; it doesn't help to modify
290 binutils/BRANCHES on a branch!
292 Please do not commit any patches to a branch you did not create
293 without the explicit permission of the person who created the branch.
295 Copyright (C) 2012-2017 Free Software Foundation, Inc.
297 Copying and distribution of this file, with or without modification,
298 are permitted in any medium without royalty provided the copyright
299 notice and this notice are preserved.
projects / thirdparty / binutils-gdb.git / blob