docs/7 - Contributing to crosstool-NG.txt
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Apr 28 00:13:41 2011 +0200 (2011-04-28)
changeset 2412 20edcd78cf67
parent 2076 b58109b7b321
child 2563 e17f35b05539
permissions -rw-r--r--
scripts/addToolsVersion: versions can be either in the .in or the .in.2

The components have their version selection handled either in the .in
file or the .in.2 file. Handle both cases.

Also, when dumping an existing version, keep the user's grep options
(ie. do override neither options nor colors).

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 File.........: 7 - Contributing to crosstool-NG.txt
     2 Copyrigth....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.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) anciens.enib.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 Patches should come with the appropriate SoB line. A SoB line is typically
    25 something like:
    26    Signed-off-by: John DOE <john.doe@somewhere.net>
    27 
    28 The SoB line is clearly described in Documentation/SubmittingPatches , section
    29 12, of your favourite Linux kernel source tree.
    30 
    31 
    32 For larger or more frequent contributions, mercurial should be used.
    33 There is a nice, complete and step-by-step tutorial in section 'C'.