X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=binutils%2FMAINTAINERS;h=afb6a4ed290be17453ba68cc28e13b6e457b9d5c;hb=53260797e5d2ddf4797b2dcf6885ea6e6357bd21;hp=e3362d2b19bd91860f6445250981fbd6375bc8f8;hpb=535b046a806667ed106d4a6b0f702283de660407;p=deliverable%2Fbinutils-gdb.git diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS index e3362d2b19..afb6a4ed29 100644 --- a/binutils/MAINTAINERS +++ b/binutils/MAINTAINERS @@ -14,14 +14,18 @@ The home page for binutils is: and patches should be sent to: - bug-binutils@gnu.org + bug-binutils@gnu.org or binutils@sources.redhat.com with "[Patch]" as part of the subject line. Note - patches to the -top level configure.in and config.sub scripts should be sent to: +top level config.guess and config.sub scripts should be sent to: config-patches@gnu.org -and not to the binutils list. +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). --------- Blanket Write Privs --------- @@ -30,12 +34,13 @@ repository without obtaining approval first: Nick Clifton (head maintainer) Richard Henderson - Ian Taylor + Ian Lance Taylor Jeff Law - Jim Wilson + Jim Wilson DJ Delorie Alan Modra - Michael Meissner + Michael Meissner + Daniel Jacobowitz --------- Maintainers --------- @@ -53,32 +58,40 @@ responsibility among the other maintainers. ALPHA Richard Henderson ARM Nick Clifton ARM Richard Earnshaw + ARM (Symbian) Paul Brook + ARM (Symbian) Mark Mitchell AVR Denis Chertykov AVR Marek Michalkiewicz - CONFIGURE Ben Elliston + BUILD SYSTEM Ben Elliston + BUILD SYSTEM Daniel Jacobowitz CRIS Hans-Peter Nilsson + CRX Tomer Levi 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] - HPPA Dave Anglin - IA-64 Jim Wilson + IA-64 Jim Wilson IQ2000 Stan Cox i860 Jason Eckhardt ix86 Alan Modra ix86 PE Christopher Faylor ix86 COFF DJ Delorie ix86 H.J.Lu - ix86 INTEL MODE Diego Novillo + ix86 INTEL MODE Jan Beulich M68HC11 M68HC12 Stephane Carrez - M68k Ben Elliston - M88k Ben Elliston + M68k Ben Elliston + M88k Mark Kettenis + MAXQ Inderpreet Singh MIPS Eric Christopher - MIPS Thiemo Seufer + MIPS Thiemo Seufer MMIX Hans-Peter Nilsson MN10300 Eric Christopher MN10300 Alexandre Oliva + MSP430 Dmitry Diky PPC Geoff Keating PPC vector ext Aldy Hernandez s390, s390x Martin Schwidefsky @@ -86,10 +99,10 @@ responsibility among the other maintainers. SH Alexandre Oliva SH Kaz Kojima SPARC Jakub Jelinek - TESTSUITES Ben Elliston - TIC4X Svein Seldal + TESTSUITES Ben Elliston + TIC4X Svein Seldal TIC54X Timothy Wall - VAX Jason R Thorpe + VAX Jason R Thorpe x86_64 Jan Hubicka x86_64 Andreas Jaeger Xtensa Bob Wilson @@ -162,3 +175,71 @@ by the binutils group. Instead they should be submitted to the config maintainer at: config-patches@gnu.org + + --------- Creating Branches --------- + +Anyone with at least write-after-approval access may create a branch +to use for their own development purposes. In keeping with FSF +policies, all patches applied to such a branch must come from people +with appropriate copyright assignments on file. All legal +requirements that would apply to any other contribution apply equally +to contributions on a branch. + +Before creating the branch, you should select a name for the branch of +the form: + + 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 +by The GNUDist Company, "tgc" would be an appropriate choice for +"org". It's up to each organization to select an appropriate choice +for "name"; some organizations may use more structure than others, so +"name" may contain additional hyphens. + +Suppose that The GNUDist Company was creating a branch to develop a +port of Binutils to the FullMonty processor. Then, an appropriate +choice of branch name would be: + + binutils-tgc-fm + +A data 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: + +1. The date should be the date that the branch was created. + +2. The date should be numerical and in the form YYYYMMDD. + +For example: + + binutils-tgc-fm_20050101 + +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 + to the initial state of your branch. + +2. Create a tag: + + cvs 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: + + cvs rtag -b -r binutils---branchpoint \ + binutils---branch + +4. Document the branch: + + Add a description of the branch to binutils/BRANCHES, and check + that file in. All branch descriptions should be added to the + HEAD revision of the file; it doesn't help to modify + binutils/BRANCHES on a branch! + +Please do not commit any patches to a branch you did not create +without the explicit permission of the person who created the branch.