docs/7 - Contributing to crosstool-NG.txt
author Yann Diorcet <diorcet.yann@gmail.com>
Mon Nov 19 21:45:09 2012 +0100 (2012-11-19)
changeset 3121 5016315d88ba
parent 2700 e8d25b041de5
permissions -rw-r--r--
binutils/binutils: simplify gold dependencies

In preparation of adding a new kernel-type, Yann D. came up
with a change in semantic on binutils/gold availability.

So far, it was architectures' responsibility to declare that
they did support binutils/gold or not. It makes much more sense
that binutils/gold declares its own availability depending on
the current architecture; after all, architectures have no way
to know wether gold supports them, while gold does know it.

Signed-off-by:Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971
     1 File.........: 7 - Contributing to crosstool-NG.txt
     2 Copyright....: (C) 2010 Yann E. MORIN <yann.morin.1998@free.fr>
     3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
     4 
     5 
     6 Contributing to crosstool-NG  /
     7 _____________________________/
     8 
     9 
    10 Sending a bug report |
    11 ---------------------+
    12 
    13 If you need to send a bug report, please send a mail with subject
    14 prefixed with "[CT_NG]" with to following destinations:
    15     TO: yann.morin.1998 (at) free.fr
    16     CC: crossgcc (at) sourceware.org
    17 
    18 
    19 Sending patches |
    20 ----------------+
    21 
    22 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
    23 
    24 When updating a package, please include the category and component in the
    25 start of the description. For example:
    26     cc/gcc: update to the Linaro 2011.09 release
    27 
    28 Here is the (mostly-complete) list of categories and components:
    29 
    30     Categories  | Components
    31     ------------+-------------------------------------------------------
    32     arch        | alpha, arm, mips, powerpc...
    33     cc          | gcc
    34     binutils    | binutils, elf2flt, sstrip
    35     libc        | eglibc, uClibc, glibc, newlib, mingw, none
    36     kernel      | linux, mingw32, bare-metal
    37     debug       | dmalloc, duma, gdb, ltrace, strace
    38     complibs    | gmp, mpfr, ppl, cloog, mpc, libelf
    39     comptools   | make, m4, autoconf, automake, libtool
    40     ------------+-------------------------------------------------------
    41                 | The following categories have no component-part:
    42     samples     | when adding/updating/removing a sample
    43     kconfig     | for stuff in the kconfig/ dir
    44     docs        | for changes to the documentation
    45     configure   | for changes to ./configure and/or Makefile.in
    46     config      | for stuff in config/ not covered above
    47     scripts     | for stuff in scripts/ not covered above
    48 
    49 
    50 Patches should come with the appropriate SoB line. A SoB line is typically
    51 something like:
    52    Signed-off-by: John DOE <john.doe@somewhere.net>
    53 
    54 The SoB line is clearly described in Documentation/SubmittingPatches , section
    55 12, of your favourite Linux kernel source tree.
    56 
    57 Add the following to your ~/.hgrc to make Mercurial check for the SoB
    58 line when committing:
    59     [hooks]
    60     pretxncommit.signoff = hg log --template '{desc}\n' -r $HG_NODE \
    61         | grep -qi '^signed-off-by:'
    62 
    63 You can also add any of the following lines if applicable:
    64     Acked-by:
    65     Tested-by:
    66     Reviewed-by:
    67 
    68 For larger or more frequent contributions, mercurial should be used.
    69 There is a nice, complete and step-by-step tutorial in section 'C'.