X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=binutils%2FMAINTAINERS;h=f21483f467654b9d171faa09f6173fb7b2f4cb37;hb=36231dfc188426d9b887af2d1c6c2cbb1c746cb3;hp=5775158cbae2e4ff104af3c352460e9a0bd668e3;hpb=0dd5bc5ebfafada237a11e66accb4848367f5073;p=deliverable%2Fbinutils-gdb.git diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS index 5775158cba..f21483f467 100644 --- a/binutils/MAINTAINERS +++ b/binutils/MAINTAINERS @@ -5,7 +5,7 @@ of the GNU Binary Utilities project. This includes the linker (ld), the assembler (gas), the profiler (gprof), a whole suite of other programs (binutils) and the libraries that they use (bfd and opcodes). This project shares a common set of header files with the -GCC and GDB projects (include), so maintainership of those files is +GCC and GDB projects (include), so maintainership of those files is shared amoungst the projects. The home page for binutils is: @@ -14,33 +14,36 @@ The home page for binutils is: and patches should be sent to: - bug-binutils@gnu.org or binutils@sources.redhat.com - + binutils@sourceware.org + with "[Patch]" as part of the subject line. Note - patches to the top level config.guess and config.sub scripts should be sent to: config-patches@gnu.org and not to the binutils lists. Patches to the other top level -configure files (configure, configure.in, config-ml.in) should +configure files (configure, configure.ac, config-ml.in) should be sent to the binutils lists, and copied to the gcc and gdb lists as well (gcc-patches@gcc.gnu.org and -gdb-patches@sources.redhat.com). +gdb-patches@sourceware.org). + +Patches to the libiberty sources should be sent to +gcc-patches@gcc.gnu.org. --------- Blanket Write Privs --------- The following people have permission to check patches into the repository without obtaining approval first: - + Nick Clifton (head maintainer) - Richard Henderson Ian Lance Taylor Jeff Law - Jim Wilson + Jim Wilson DJ Delorie - Alan Modra + Alan Modra Michael Meissner - Daniel Jacobowitz + Daniel Jacobowitz + Richard Sandiford --------- Maintainers --------- @@ -55,66 +58,114 @@ maintainers for a given domain then responsibility falls to the first maintainer. The first maintainer is free to devolve that responsibility among the other maintainers. - ALPHA Richard Henderson + ALPHA Richard Henderson + AARCH64 Richard Earnshaw + AARCH64 Marcus Shawcroft + ARC Claudiu Zissulescu ARM Nick Clifton ARM Richard Earnshaw - ARM (Symbian) Paul Brook - ARM (Symbian) Mark Mitchell - AVR Denis Chertykov + ARM Ramana Radhakrishnan + AVR Denis Chertykov AVR Marek Michalkiewicz - BFIN Jie Zhang - BFIN Bernd Schmidt - BUILD SYSTEM Ben Elliston - BUILD SYSTEM Daniel Jacobowitz + BFIN Jie Zhang + BFIN Mike Frysinger + BPF Jose E. Marchesi + BUILD SYSTEM Daniel Jacobowitz + CR16 M R Swami Reddy CRIS Hans-Peter Nilsson - CRX Tomer Levi + CRX M R Swami Reddy + CTF Nick Alcock + C-SKY Lifang Xia + C-SKY Yunhai Shang DLX Nikolaos Kavvadias DWARF2 Jason Merrill - FR30 Dave Brolley - FRV Dave Brolley + DWARF2 Jakub Jelinek + dwarf-mode.el Tom Tromey + EPIPHANY Joern Rennecke + FR30 Nick Clifton + FRV Nick Clifton FRV Alexandre Oliva - H8300 Anil Paranjpe - HPPA Dave Anglin - HPPA elf32 Alan Modra + GOLD Ian Lance Taylor + GOLD Cary Coutant + H8300 Prafulla Thakare + HPPA Dave Anglin + HPPA elf32 Alan Modra HPPA elf64 Jeff Law [Basic maintainance only] - IA-64 Jim Wilson + IA-64 Jim Wilson IQ2000 Stan Cox - i860 Jason Eckhardt - ix86 Alan Modra - ix86 PE Christopher Faylor + ix86 H.J. Lu + ix86 PE Christopher Faylor ix86 COFF DJ Delorie - ix86 H.J. Lu + ix86 PE/COFF Dave Korn ix86 INTEL MODE Jan Beulich - M68HC11 M68HC12 Stephane Carrez - M68k Ben Elliston - M88k Mark Kettenis + LM32 Jon Beniston + M32R Doug Evans + M68HC11 M68HC12 Stephane Carrez + M68HC11 M68HC12 Sean Keys + MACH-O Tristan Gingold MAXQ Inderpreet Singh - MEP Dave Brolley - MIPS Eric Christopher - MIPS Thiemo Seufer + MEP Nick Clifton + METAG Markos Chandras + MICROBLAZE Michael Eager + MIPS Chenghua Xu + MIPS I-IV Maciej W. Rozycki MMIX Hans-Peter Nilsson - MN10300 Eric Christopher MN10300 Alexandre Oliva + Moxie Anthony Green MSP430 Dmitry Diky + NDS32 Kuan-Lin Chen + NDS32 Wei-Cheng Wang + NetBSD support Matt Thomas + Nios II Sandra Loosemore + Nios II Andrew Jenner + OR1K Christian Svensson + OR1K Stefan Kristiansson PPC Geoff Keating + PPC Alan Modra + PPC Peter Bergner PPC vector ext Aldy Hernandez + RISC-V Palmer Dabbelt + RISC-V Andrew Waterman + RISC-V Jim Wilson + RX Nick Clifton + S12Z John Darrington s390, s390x Martin Schwidefsky - SCORE Mei Ligang + s390, s390x Andreas Krebbel SH Alexandre Oliva - SH Kaz Kojima - SPARC Jakub Jelinek - TESTSUITES Ben Elliston - TIC4X Svein Seldal + SPARC David S. Miller + SPARC Jose E. Marchesi + SPU Alan Modra TIC54X Timothy Wall - VAX Jason R Thorpe + TIC6X Joseph Myers + TILE-Gx Walter Lee + TILEPro Walter Lee + VAX Matt Thomas VAX Jan-Benedict Glaw + Visium Eric Botcazou + VMS Tristan Gingold x86_64 Jan Hubicka x86_64 Andreas Jaeger - x86_64 H.J. Lu - Xtensa Bob Wilson - z80 Arnold Metselaar + x86_64 H.J. Lu + XCOFF Richard Sandiford + XGATE Sean Keys + Xtensa Sterling Augustine z8k Christian Groessler + --------- Past Maintainers ------------- + +These folks have acted as maintainers in the past, but have now +moved on to other things. Our thanks for all their hard work +goes with them. + + Paul Brook + Eric Christopher + Jason Eckhardt + Mark Kettenis + Mei Ligang + Arnold Metselaar + Mark Mitchell + Bernd Schmidt + Svein Seldal --------- CGEN Maintainers ------------- @@ -122,11 +173,11 @@ CGEN is a tool for building, amongst other things, assemblers, disassemblers and simulators from a single description of a CPU. It creates files in several of the binutils directories, but it is mentioned here since there is a single group that maintains -CGEN and the files that it creates. +CGEN and the files that it creates. If you have CGEN related problems you can send email to; - cgen@sources.redhat.com + cgen@sourceware.org The current CGEN maintainers are: @@ -159,18 +210,18 @@ If a patch is approved for check in to the mainline sources, it can also be checked into the current release branch. Normally however only bug fixes should be applied to the branch. New features, new ports, etc, should be restricted to the mainline. (Otherwise the -burden of maintaining the branch in sync with the mainline becomes too +burden of maintaining the branch in sync with the mainline becomes too great). If you are uncertain as to whether a patch is appropriate for the branch, ask the branch maintainer. This is: - Daniel Jacobowitz + (cf global maintainers) -------- Testsuites --------------- In general patches to any of the binutils testsuites should be considered generic and sent to the binutils mailing list for approval. Patches to target specific tests are the responsibility the -relevent port maintainer(s), and can be approved/checked in by them. +relevant port maintainer(s), and can be approved/checked in by them. Other testsuite patches need the approval of a blanket-write-priveleges person. @@ -195,7 +246,7 @@ to contributions on a branch. Before creating the branch, you should select a name for the branch of the form: - binutils-- + binutils-- where "org" is the initials of your organization, or your own initials if you are acting as an individual. For example, for a branch created @@ -210,7 +261,7 @@ choice of branch name would be: binutils-tgc-fm -A data stamp is not required as part of the name field, but some +A date stamp is not required as part of the name field, but some organizations like to have one. If you do include the date, you should follow these rules: @@ -226,20 +277,20 @@ would be appropriate if the branch was created on January 1st, 2005. Having selected the branch name, create the branch as follows: -1. Check out binutils, so that you have a CVS checkout corresponding +1. Check out binutils, so that you have a git checkout corresponding to the initial state of your branch. 2. Create a tag: - cvs tag binutils---branchpoint + git tag binutils---branchpoint That tag will allow you, and others, to easily determine what's changed on the branch relative to the initial state. -3. Create the branch: +3. Create and push the branch: - cvs rtag -b -r binutils---branchpoint \ - binutils---branch + git checkout -b binutils---branch + git push origin HEAD 4. Document the branch: @@ -250,3 +301,9 @@ Having selected the branch name, create the branch as follows: Please do not commit any patches to a branch you did not create without the explicit permission of the person who created the branch. + +Copyright (C) 2012-2020 Free Software Foundation, Inc. + +Copying and distribution of this file, with or without modification, +are permitted in any medium without royalty provided the copyright +notice and this notice are preserved.