Adding myself as DLX maintainer

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Adding myself as DLX maintainer

Hash: SHA1
Hi there

i have properly signed the copyright assignment form for binutils
which was also signed by the executive director of the FSF.

That said, may I add myself as DLX maintainer?

I have attached a modified /src/binutils/MAINTAINERS file with the
additional line in the maintainers list.

Nikolaos Kavvadias

Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird -

                ========= Binutils Maintainers =========

This is the list of individuals responsible for maintenance and update
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
shared amoungst the projects.

The home page for binutils is:

and patches should be sent to:

  [hidden email]    or    [hidden email]
with "[Patch]" as part of the subject line.  Note - patches to the
top level config.guess and config.sub scripts should be sent to:

  [hidden email]

and not to the binutils lists.  Patches to the other top level
configure files (configure,, should
be sent to the binutils lists, and copied to the gcc and gdb
lists as well ([hidden email] and
[hidden email]).

                --------- Blanket Write Privs ---------

The following people have permission to check patches into the
repository without obtaining approval first:
  Nick Clifton <[hidden email]> (head maintainer)
  Richard Henderson <[hidden email]>
  Ian Lance Taylor <[hidden email]>
  Jeff Law <[hidden email]>
  Jim Wilson <[hidden email]>
  DJ Delorie <[hidden email]>
  Alan Modra <[hidden email]>
  Michael Meissner <[hidden email]>
  Daniel Jacobowitz <[hidden email]>

      --------- Maintainers ---------

Maintainers are individuals who are responsible for, and have
permission to check in changes in, certain subsets of the code.  Note
that maintainers still need approval to check in changes outside of
the immediate domain that they maintain.

If there is no maintainer for a given domain then the responsibility
falls to the head maintainer (above).  If there are several
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 <[hidden email]>
  ARM   Nick Clifton <[hidden email]>
  ARM   Richard Earnshaw <[hidden email]>
  ARM (Symbian)   Paul Brook <[hidden email]>
  ARM (Symbian)   Mark Mitchell <[hidden email]>
  AVR   Denis Chertykov <[hidden email]>
  AVR   Marek Michalkiewicz <[hidden email]>
  BFIN   Jie Zhang <[hidden email]>
  BFIN   Bernd Schmidt <[hidden email]>
  BUILD SYSTEM   Ben Elliston <[hidden email]>
  BUILD SYSTEM   Daniel Jacobowitz <[hidden email]>
  CRIS   Hans-Peter Nilsson <[hidden email]>
  CRX   Tomer Levi <[hidden email]>
  DLX              Nikolaos Kavvadias <[hidden email]>
  DWARF2   Jason Merrill <[hidden email]>
  FR30   Dave Brolley <[hidden email]>
  FRV   Dave Brolley <[hidden email]>
  FRV   Alexandre Oliva <[hidden email]>
  H8300   Anil Paranjpe <[hidden email]>
  HPPA   Dave Anglin <[hidden email]>
  HPPA elf32   Alan Modra <[hidden email]>
  HPPA elf64   Jeff Law <[hidden email]> [Basic maintainance only]
  IA-64   Jim Wilson <[hidden email]>
  IQ2000   Stan Cox <[hidden email]>
  i860   Jason Eckhardt <[hidden email]>
  ix86   Alan Modra <[hidden email]>
  ix86 PE   Christopher Faylor <[hidden email]>
  ix86 COFF   DJ Delorie <[hidden email]>
  ix86   H.J.Lu <[hidden email]>
  ix86 INTEL MODE  Jan Beulich <[hidden email]>
  M68HC11 M68HC12  Stephane Carrez <[hidden email]>
  M68k   Ben Elliston <[hidden email]>
  M88k   Mark Kettenis <[hidden email]>
  MAXQ   Inderpreet Singh <[hidden email]>
  MIPS   Eric Christopher <[hidden email]>
  MIPS   Thiemo Seufer <[hidden email]>
  MMIX   Hans-Peter Nilsson <[hidden email]>
  MN10300   Eric Christopher <[hidden email]>
  MN10300   Alexandre Oliva <[hidden email]>
  MSP430   Dmitry Diky <[hidden email]>
  PPC   Geoff Keating <[hidden email]>
  PPC vector ext   Aldy Hernandez <[hidden email]>
  s390, s390x   Martin Schwidefsky <[hidden email]>
  SH   Jörn Rennecke <[hidden email]>
  SH   Alexandre Oliva <[hidden email]>
  SH   Kaz Kojima <[hidden email]>
  SPARC   Jakub Jelinek <[hidden email]>
  TESTSUITES   Ben Elliston <[hidden email]>
  TIC4X            Svein Seldal <[hidden email]>
  TIC54X           Timothy Wall <[hidden email]>
  VAX   Jason R Thorpe <[hidden email]>
  VAX   Jan-Benedict Glaw <[hidden email]>
  x86_64   Jan Hubicka <[hidden email]>
  x86_64   Andreas Jaeger <[hidden email]>
  x86_64   H.J.Lu <[hidden email]>
  Xtensa   Bob Wilson <[hidden email]>
  z80   Arnold Metselaar <[hidden email]>
  z8k   Christian Groessler <[hidden email]>

      --------- CGEN Maintainers -------------

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.

If you have CGEN related problems you can send email to;

   [hidden email]

The current CGEN maintainers are:

  Doug Evans, Ben Elliston, Frank Eigler

     --------- Write After Approval ---------

Individuals with "write after approval" have the ability to check in
changes, but they must get approval for each change from someone in
one of the above lists (blanket write or maintainers).

[It's a huge list, folks.  You know who you are.  If you have the
 *ability* to do binutils checkins, you're in this group.  Just
 remember to get approval before checking anything in.]

     -------------  Obvious Fixes -------------

Fixes for obvious mistakes do not need approval, and can be checked in
right away, but the patch should still be sent to the binutils list.
The definition of obvious is a bit hazy, and if you are not sure, then
you should seek approval first.  Obvious fixes include fixes for
spelling mistakes, blatantly incorrect code (where the correct code is
also blatantly obvious), and so on.  Obvious fixes should always be
small, the larger they are, the more likely it is that they contain
some un-obvious side effect or consequence.

    --------- Branch Checkins ---------

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
great).  If you are uncertain as to whether a patch is appropriate for
the branch, ask the branch maintainer.  This is:

   Daniel Jacobowitz  <[hidden email]>

    -------- 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.
Other testsuite patches need the approval of a blanket-write-priveleges

    -------- Configure patches ----------

Patches to the top level configure files (config.sub & config.guess)
are not the domain of the binutils project and they cannot be approved
by the binutils group.  Instead they should be submitted to the config
maintainer at:

        [hidden email]

    --------- 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:


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:


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:


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-<org>-<name>-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-<org>-<name>-branchpoint \

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.