X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=binutils%2FMAINTAINERS;h=a3fdce3060513dcf0f62f7ba2c4ea6f9f841bf7f;hb=7df428b11639efa0ec64b3f10a2472bd68316179;hp=eed6e078e0ce7112478b085007f80cba5f2b5131;hpb=41772c33cab64429d9feea6c0de75cca35b67219;p=deliverable%2Fbinutils-gdb.git diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS index eed6e078e0..a3fdce3060 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,8 +14,8 @@ 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: @@ -25,13 +25,13 @@ and not to the binutils lists. Patches to the other top level configure files (configure, configure.in, 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). --------- 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 @@ -58,18 +58,22 @@ responsibility among the other maintainers. ALPHA Richard Henderson ARM Nick Clifton ARM Richard Earnshaw - ARM (Symbian) Paul Brook + ARM Paul Brook ARM (Symbian) Mark Mitchell AVR Denis Chertykov AVR Marek Michalkiewicz + BFIN Jie Zhang + BFIN Bernd Schmidt BUILD SYSTEM Ben Elliston BUILD SYSTEM Daniel Jacobowitz CRIS Hans-Peter Nilsson CRX Tomer Levi + DLX Nikolaos Kavvadias DWARF2 Jason Merrill FR30 Dave Brolley FRV Dave Brolley FRV Alexandre Oliva + H8300 Anil Paranjpe HPPA Dave Anglin HPPA elf32 Alan Modra HPPA elf64 Jeff Law [Basic maintainance only] @@ -79,29 +83,38 @@ responsibility among the other maintainers. ix86 Alan Modra ix86 PE Christopher Faylor ix86 COFF DJ Delorie - ix86 H.J.Lu + ix86 H.J. Lu + ix86 INTEL MODE Jan Beulich M68HC11 M68HC12 Stephane Carrez M68k Ben Elliston + M88k Mark Kettenis MAXQ Inderpreet Singh - MIPS Eric Christopher - MIPS Thiemo Seufer + MEP Dave Brolley + MIPS Eric Christopher + MIPS Thiemo Seufer MMIX Hans-Peter Nilsson - MN10300 Eric Christopher + MN10300 Eric Christopher MN10300 Alexandre Oliva + MSP430 Dmitry Diky + NetBSD support Matt Thomas PPC Geoff Keating + PPC Alan Modra PPC vector ext Aldy Hernandez s390, s390x Martin Schwidefsky - SH Jörn Rennecke + SCORE Mei Ligang SH Alexandre Oliva SH Kaz Kojima SPARC Jakub Jelinek TESTSUITES Ben Elliston TIC4X Svein Seldal TIC54X Timothy Wall - VAX Jason R Thorpe + VAX Matt Thomas + VAX Jan-Benedict Glaw x86_64 Jan Hubicka x86_64 Andreas Jaeger + x86_64 H.J. Lu Xtensa Bob Wilson + z80 Arnold Metselaar z8k Christian Groessler @@ -111,15 +124,15 @@ 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: - Doug Evans, Ben Elliston, Frank Eigler + Doug Evans, Frank Eigler --------- Write After Approval --------- @@ -148,7 +161,7 @@ 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: @@ -184,7 +197,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 @@ -228,7 +241,7 @@ Having selected the branch name, create the branch as follows: 3. Create the branch: cvs rtag -b -r binutils---branchpoint \ - binutils---branch + binutils---branch 4. Document the branch: