README
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Aug 07 18:30:45 2009 +0200 (2009-08-07)
changeset 1465 f0d113f0820e
parent 1464 a306f9b4f48b
child 1466 1bacd35b57e6
permissions -rw-r--r--
Add sections to the README
     1 This is the README for crosstool-NG
     2 
     3 TABLE OF CONTENT /
     4 ________________/
     5 
     6   - GETTING STARTED
     7   - PARTICIPATING
     8     - Sending a bug report
     9     - Sending patches
    10   - CREDITS
    11   - KNOWN ISSUES
    12 
    13 
    14 GETTING STARTED /
    15 _______________/
    16 
    17 To get you started, just enter:
    18   ./configure --help
    19 
    20 You can find a (terse and WIP) documentation in docs/overview.txt.
    21 
    22 You can also point your browser to
    23   http://ymorin.is-a-geek.org/projects/crosstool
    24 
    25 PARTICIPATING /
    26 _____________/
    27 
    28 Sending a bug report
    29 --------------------
    30 
    31 If you need to send a bug report, please send a mail with subject
    32  prefixed with "[CT_NG]" with to following destinations:
    33      TO: yann.morin.1998 (at) anciens.enib.fr
    34      CC: crossgcc (at) sourceware.org
    35 
    36 Sending patches
    37 ---------------
    38 
    39 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
    40 
    41 Patches should come with the appropriate SoB line. A SoB line is typically
    42  something like:
    43    Signed-off-by: John DOE <john.doe@somewhere.net>
    44 
    45 The SoB line is clearly described in Documentation/SubmittingPatches , section
    46 12, of your favourite Linux kernel source tree.
    47 
    48 CREDITS /
    49 _______/
    50 
    51 The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
    52 
    53 KNOWN ISSUES /
    54 ____________/
    55 
    56 The list of known issues is listed in docs/known-issues.txt.
    57 
    58 Aloha!