Commit | Line | Data |
---|---|---|
302ab118 DD |
1 | ========= Binutils Maintainers ========= |
2 | ||
3 | This is the list of individuals responsible for maintenance and update | |
1b577b00 NC |
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 | |
eacf2b70 | 8 | GCC and GDB projects (include), so maintainership of those files is |
1b577b00 | 9 | shared amoungst the projects. |
302ab118 | 10 | |
1b577b00 | 11 | The home page for binutils is: |
8c2bc687 | 12 | |
1b577b00 NC |
13 | http://www.gnu.org/software/binutils/binutils.html |
14 | ||
15 | and patches should be sent to: | |
16 | ||
eacf2b70 AM |
17 | binutils@sourceware.org |
18 | ||
1b577b00 | 19 | with "[Patch]" as part of the subject line. Note - patches to the |
04fbe429 | 20 | top level config.guess and config.sub scripts should be sent to: |
302ab118 | 21 | |
1b577b00 | 22 | config-patches@gnu.org |
302ab118 | 23 | |
04fbe429 | 24 | and not to the binutils lists. Patches to the other top level |
73fb7068 RS |
25 | configure files (configure, configure.in, config-ml.in) should |
26 | be sent to the binutils lists, and copied to the gcc and gdb | |
04fbe429 | 27 | lists as well (gcc-patches@gcc.gnu.org and |
eacf2b70 | 28 | gdb-patches@sourceware.org). |
1b577b00 NC |
29 | |
30 | --------- Blanket Write Privs --------- | |
302ab118 | 31 | |
1b577b00 NC |
32 | The following people have permission to check patches into the |
33 | repository without obtaining approval first: | |
eacf2b70 | 34 | |
1b577b00 | 35 | Nick Clifton <nickc@redhat.com> (head maintainer) |
3517749c | 36 | Ian Lance Taylor <ian@airs.com> |
1b577b00 | 37 | Jeff Law <law@redhat.com> |
4b3be0b6 | 38 | Jim Wilson <wilson@tuliptree.org> |
1b577b00 | 39 | DJ Delorie <dj@redhat.com> |
ebc5095a | 40 | Alan Modra <amodra@gmail.com> |
2445335e | 41 | Michael Meissner <gnu@the-meissners.org> |
9483a6ee | 42 | Daniel Jacobowitz <drow@false.org> |
93abc97a | 43 | Richard Sandiford <rdsandiford@googlemail.com> |
1b577b00 NC |
44 | |
45 | --------- Maintainers --------- | |
46 | ||
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. | |
302ab118 DD |
51 | |
52 | If there is no maintainer for a given domain then the responsibility | |
1b577b00 NC |
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. | |
57 | ||
2141b110 | 58 | ALPHA Richard Henderson <rth@twiddle.net> |
a06ea964 | 59 | AARCH64 Richard Earnshaw <rearnsha@arm.com> |
5b2ab150 | 60 | AARCH64 Marcus Shawcroft <marcus.shawcroft@arm.com> |
1b577b00 | 61 | ARM Nick Clifton <nickc@redhat.com> |
3a7e524e | 62 | ARM Richard Earnshaw <rearnsha@arm.com> |
6c1965f9 | 63 | ARM Ramana Radhakrishnan <ramana.radhakrishnan@arm.com> |
e8b338d0 | 64 | AVR Denis Chertykov <chertykov@gmail.com> |
e0159aa9 | 65 | AVR Marek Michalkiewicz <marekm@amelek.gda.pl> |
4161fbb0 | 66 | BFIN Jie Zhang <jzhang918@gmail.com> |
3d5ff620 | 67 | BFIN Mike Frysinger <vapier@gentoo.org> |
9483a6ee | 68 | BUILD SYSTEM Daniel Jacobowitz <drow@false.org> |
ec8cbbf6 | 69 | CR16 M R Swami Reddy <MR.Swami.Reddy@nsc.com> |
1b577b00 | 70 | CRIS Hans-Peter Nilsson <hp@axis.com> |
ec8cbbf6 | 71 | CRX M R Swami Reddy <MR.Swami.Reddy@nsc.com> |
4b3dc01d | 72 | DLX Nikolaos Kavvadias <nkavv@physics.auth.gr> |
1b577b00 | 73 | DWARF2 Jason Merrill <jason@redhat.com> |
1cd48f98 | 74 | DWARF2 Jakub Jelinek <jakub@redhat.com> |
be459434 | 75 | dwarf-mode.el Tom Tromey <tom@tromey.com> |
5b169225 | 76 | EPIPHANY Joern Rennecke <joern.rennecke@embecosm.com> |
a9f0b5e7 DB |
77 | FR30 Dave Brolley <brolley@redhat.com> |
78 | FRV Dave Brolley <brolley@redhat.com> | |
ec2dfb42 | 79 | FRV Alexandre Oliva <aoliva@redhat.com> |
ee441d9a | 80 | GOLD Ian Lance Taylor <iant@google.com> |
08e4f608 | 81 | GOLD Cary Coutant <ccoutant@gmail.com> |
db448d50 | 82 | H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com> |
6b10f68d | 83 | HPPA Dave Anglin <dave.anglin@nrc.ca> |
ebc5095a | 84 | HPPA elf32 Alan Modra <amodra@gmail.com> |
f52e0eb8 | 85 | HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only] |
4b3be0b6 | 86 | IA-64 Jim Wilson <wilson@tuliptree.org> |
3b36097d | 87 | IQ2000 Stan Cox <scox@redhat.com> |
d68c07bb | 88 | i860 Jason Eckhardt <jle@rice.edu> |
ccdb9c9f | 89 | ix86 H.J. Lu <hjl.tools@gmail.com> |
bd5a94b0 | 90 | ix86 PE Christopher Faylor <me+binutils@cgf.cx> |
b54e7460 | 91 | ix86 COFF DJ Delorie <dj@redhat.com> |
57f6e0bc | 92 | ix86 PE/COFF Dave Korn <dave.korn.cygwin@gmail.com> |
53260797 | 93 | ix86 INTEL MODE Jan Beulich <jbeulich@novell.com> |
84e94c90 | 94 | LM32 Jon Beniston <jon@beniston.com> |
5d0c4f10 | 95 | M32R Doug Evans <dje@sebabeach.org> |
a481d14b | 96 | M68HC11 M68HC12 Stephane Carrez <Stephane.Carrez@gmail.com> |
554adb2c | 97 | M68HC11 M68HC12 Sean Keys <skeys@ipdatasys.com> |
163730f0 | 98 | M88k Mark Kettenis <kettenis@gnu.org> |
c91933e9 | 99 | MACH-O Tristan Gingold <tgingold@free.fr> |
c4cf3821 | 100 | MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com> |
0dd5bc5e | 101 | MEP Dave Brolley <brolley@redhat.com> |
d5c7e0e9 | 102 | METAG Markos Chandras <markos.chandras@imgtec.com> |
7ba29e2a | 103 | MICROBLAZE Michael Eager <eager@eagercon.com> |
16e1d727 | 104 | MIPS Maciej W. Rozycki <macro@imgtec.com> |
9b19141a | 105 | MMIX Hans-Peter Nilsson <hp@bitrange.com> |
91593c9d | 106 | MN10300 Alexandre Oliva <aoliva@redhat.com> |
17eb60e9 | 107 | Moxie Anthony Green <green@moxielogic.com> |
1acfb01b | 108 | MSP430 Dmitry Diky <diwil@spec.ru> |
35c08157 KLC |
109 | NDS32 Kuan-Lin Chen <kuanlinchentw@gmail.com> |
110 | NDS32 Wei-Cheng Wang <cole945@gmail.com> | |
5ad507ee | 111 | NetBSD support Matt Thomas <matt@netbsd.org> |
36591ba1 SL |
112 | Nios II Sandra Loosemore <sandra@codesourcery.com> |
113 | Nios II Andrew Jenner <andrew@codesourcery.com> | |
b2bcb4bd CS |
114 | OR1K Christian Svensson <blue@cmd.nu> |
115 | OR1K Stefan Kristiansson <stefan.kristiansson@saunalahti.fi> | |
a926ab2f | 116 | PPC Geoff Keating <geoffk@geoffk.org> |
ebc5095a | 117 | PPC Alan Modra <amodra@gmail.com> |
4bc0608a | 118 | PPC Peter Bergner <bergner@vnet.ibm.com> |
42ea8716 | 119 | PPC vector ext Aldy Hernandez <aldyh@redhat.com> |
180093c7 PD |
120 | RISC-V Palmer Dabbelt <palmer@sifive.com> |
121 | RISC-V Andrew Waterman <andrew@sifive.com> | |
016f5a37 | 122 | RISC-V Jim Wilson <jimw@sifive.com> |
99c513f6 | 123 | RL78 DJ Delorie <dj@redhat.com> |
c7927a3c NC |
124 | RX DJ Delorie <dj@redhat.com> |
125 | RX Nick Clifton <nickc@redhat.com> | |
54589086 | 126 | s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com> |
6604eb5f | 127 | s390, s390x Andreas Krebbel <krebbel@linux.vnet.ibm.com> |
9f77fa06 | 128 | SH Alexandre Oliva <aoliva@redhat.com> |
cdd30861 | 129 | SPARC David S. Miller <davem@davemloft.net> |
9b5481c6 | 130 | SPARC Jose E. Marchesi <jose.marchesi@oracle.com> |
ebc5095a | 131 | SPU Alan Modra <amodra@gmail.com> |
6e917903 | 132 | TIC54X Timothy Wall <twall@alum.mit.edu> |
40b36596 | 133 | TIC6X Joseph Myers <joseph@codesourcery.com> |
ab8b6d29 WL |
134 | TILE-Gx Walter Lee <walt@tilera.com> |
135 | TILEPro Walter Lee <walt@tilera.com> | |
5ad507ee | 136 | VAX Matt Thomas <matt@netbsd.org> |
677c6f3a | 137 | VAX Jan-Benedict Glaw <jbglaw@lug-owl.de> |
2a6969e1 | 138 | Visium Eric Botcazou <ebotcazou@libertysurf.fr> |
c91933e9 | 139 | VMS Tristan Gingold <tgingold@free.fr> |
91593c9d AM |
140 | x86_64 Jan Hubicka <jh@suse.cz> |
141 | x86_64 Andreas Jaeger <aj@suse.de> | |
fabda5a7 | 142 | x86_64 H.J. Lu <hjl.tools@gmail.com> |
93abc97a | 143 | XCOFF Richard Sandiford <r.sandiford@uk.ibm.com> |
8d88d7ec | 144 | XGATE Sean Keys <skeys@ipdatasys.com> |
3aade688 | 145 | Xtensa Sterling Augustine <augustine.sterling@gmail.com> |
190668a2 | 146 | z80 Arnold Metselaar <arnold.metselaar@planet.nl> |
3c25c5f6 NC |
147 | z8k Christian Groessler <chris@groessler.org> |
148 | ||
13364275 NC |
149 | --------- Past Maintainers ------------- |
150 | ||
151 | These folks have acted as maintainers in the past, but have now | |
152 | moved on to other things. Our thanks for all their hard work | |
153 | goes with them. | |
154 | ||
fd13a84b | 155 | Paul Brook |
7c723eec | 156 | Eric Christopher |
71d01c69 | 157 | Mei Ligang |
13364275 | 158 | Mark Mitchell |
cf581a9b | 159 | Bernd Schmidt |
482366c3 | 160 | Svein Seldal |
1b577b00 NC |
161 | |
162 | --------- CGEN Maintainers ------------- | |
dac850af | 163 | |
08c404a5 | 164 | CGEN is a tool for building, amongst other things, assemblers, |
1b577b00 NC |
165 | disassemblers and simulators from a single description of a CPU. |
166 | It creates files in several of the binutils directories, but it | |
167 | is mentioned here since there is a single group that maintains | |
eacf2b70 | 168 | CGEN and the files that it creates. |
dac850af NC |
169 | |
170 | If you have CGEN related problems you can send email to; | |
171 | ||
eacf2b70 | 172 | cgen@sourceware.org |
dac850af NC |
173 | |
174 | The current CGEN maintainers are: | |
175 | ||
b893fd29 | 176 | Doug Evans, Frank Eigler |
302ab118 | 177 | |
1b577b00 | 178 | --------- Write After Approval --------- |
302ab118 DD |
179 | |
180 | Individuals with "write after approval" have the ability to check in | |
181 | changes, but they must get approval for each change from someone in | |
182 | one of the above lists (blanket write or maintainers). | |
183 | ||
184 | [It's a huge list, folks. You know who you are. If you have the | |
1b577b00 NC |
185 | *ability* to do binutils checkins, you're in this group. Just |
186 | remember to get approval before checking anything in.] | |
a9f10786 | 187 | |
1b577b00 | 188 | ------------- Obvious Fixes ------------- |
a9f10786 NC |
189 | |
190 | Fixes for obvious mistakes do not need approval, and can be checked in | |
191 | right away, but the patch should still be sent to the binutils list. | |
192 | The definition of obvious is a bit hazy, and if you are not sure, then | |
193 | you should seek approval first. Obvious fixes include fixes for | |
194 | spelling mistakes, blatantly incorrect code (where the correct code is | |
195 | also blatantly obvious), and so on. Obvious fixes should always be | |
196 | small, the larger they are, the more likely it is that they contain | |
197 | some un-obvious side effect or consequence. | |
90ab7e9a | 198 | |
1b577b00 | 199 | --------- Branch Checkins --------- |
90ab7e9a NC |
200 | |
201 | If a patch is approved for check in to the mainline sources, it can | |
202 | also be checked into the current release branch. Normally however | |
203 | only bug fixes should be applied to the branch. New features, new | |
204 | ports, etc, should be restricted to the mainline. (Otherwise the | |
eacf2b70 | 205 | burden of maintaining the branch in sync with the mainline becomes too |
90ab7e9a NC |
206 | great). If you are uncertain as to whether a patch is appropriate for |
207 | the branch, ask the branch maintainer. This is: | |
208 | ||
c91933e9 | 209 | (cf global maintainers) |
873e0588 NC |
210 | |
211 | -------- Testsuites --------------- | |
212 | ||
213 | In general patches to any of the binutils testsuites should be | |
214 | considered generic and sent to the binutils mailing list for | |
215 | approval. Patches to target specific tests are the responsibility the | |
13364275 | 216 | relevant port maintainer(s), and can be approved/checked in by them. |
873e0588 NC |
217 | Other testsuite patches need the approval of a blanket-write-priveleges |
218 | person. | |
219 | ||
220 | -------- Configure patches ---------- | |
221 | ||
222 | Patches to the top level configure files (config.sub & config.guess) | |
223 | are not the domain of the binutils project and they cannot be approved | |
224 | by the binutils group. Instead they should be submitted to the config | |
225 | maintainer at: | |
226 | ||
227 | config-patches@gnu.org | |
619b8b60 MM |
228 | |
229 | --------- Creating Branches --------- | |
230 | ||
231 | Anyone with at least write-after-approval access may create a branch | |
232 | to use for their own development purposes. In keeping with FSF | |
233 | policies, all patches applied to such a branch must come from people | |
234 | with appropriate copyright assignments on file. All legal | |
235 | requirements that would apply to any other contribution apply equally | |
236 | to contributions on a branch. | |
237 | ||
238 | Before creating the branch, you should select a name for the branch of | |
239 | the form: | |
240 | ||
eacf2b70 | 241 | binutils-<org>-<name> |
619b8b60 MM |
242 | |
243 | where "org" is the initials of your organization, or your own initials | |
244 | if you are acting as an individual. For example, for a branch created | |
245 | by The GNUDist Company, "tgc" would be an appropriate choice for | |
246 | "org". It's up to each organization to select an appropriate choice | |
247 | for "name"; some organizations may use more structure than others, so | |
248 | "name" may contain additional hyphens. | |
249 | ||
250 | Suppose that The GNUDist Company was creating a branch to develop a | |
251 | port of Binutils to the FullMonty processor. Then, an appropriate | |
252 | choice of branch name would be: | |
253 | ||
254 | binutils-tgc-fm | |
255 | ||
45781998 | 256 | A date stamp is not required as part of the name field, but some |
619b8b60 MM |
257 | organizations like to have one. If you do include the date, you |
258 | should follow these rules: | |
259 | ||
260 | 1. The date should be the date that the branch was created. | |
261 | ||
262 | 2. The date should be numerical and in the form YYYYMMDD. | |
263 | ||
264 | For example: | |
265 | ||
266 | binutils-tgc-fm_20050101 | |
267 | ||
268 | would be appropriate if the branch was created on January 1st, 2005. | |
269 | ||
270 | Having selected the branch name, create the branch as follows: | |
271 | ||
20cef68c | 272 | 1. Check out binutils, so that you have a git checkout corresponding |
619b8b60 MM |
273 | to the initial state of your branch. |
274 | ||
275 | 2. Create a tag: | |
276 | ||
20cef68c | 277 | git tag binutils-<org>-<name>-branchpoint |
619b8b60 MM |
278 | |
279 | That tag will allow you, and others, to easily determine what's | |
280 | changed on the branch relative to the initial state. | |
281 | ||
20cef68c | 282 | 3. Create and push the branch: |
619b8b60 | 283 | |
20cef68c TT |
284 | git checkout -b binutils-<org>-<name>-branch |
285 | git push origin HEAD | |
619b8b60 MM |
286 | |
287 | 4. Document the branch: | |
288 | ||
289 | Add a description of the branch to binutils/BRANCHES, and check | |
290 | that file in. All branch descriptions should be added to the | |
291 | HEAD revision of the file; it doesn't help to modify | |
292 | binutils/BRANCHES on a branch! | |
293 | ||
294 | Please do not commit any patches to a branch you did not create | |
295 | without the explicit permission of the person who created the branch. | |
5bf135a7 | 296 | \f |
2571583a | 297 | Copyright (C) 2012-2017 Free Software Foundation, Inc. |
5bf135a7 NC |
298 | |
299 | Copying and distribution of this file, with or without modification, | |
300 | are permitted in any medium without royalty provided the copyright | |
301 | notice and this notice are preserved. |