1.1 --- a/README Fri Aug 07 18:25:54 2009 +0200
1.2 +++ b/README Fri Aug 07 18:30:45 2009 +0200
1.3 @@ -1,5 +1,19 @@
1.4 This is the README for crosstool-NG
1.5
1.6 +TABLE OF CONTENT /
1.7 +________________/
1.8 +
1.9 + - GETTING STARTED
1.10 + - PARTICIPATING
1.11 + - Sending a bug report
1.12 + - Sending patches
1.13 + - CREDITS
1.14 + - KNOWN ISSUES
1.15 +
1.16 +
1.17 +GETTING STARTED /
1.18 +_______________/
1.19 +
1.20 To get you started, just enter:
1.21 ./configure --help
1.22
1.23 @@ -8,22 +22,37 @@
1.24 You can also point your browser to
1.25 http://ymorin.is-a-geek.org/projects/crosstool
1.26
1.27 +PARTICIPATING /
1.28 +_____________/
1.29 +
1.30 +Sending a bug report
1.31 +--------------------
1.32 +
1.33 +If you need to send a bug report, please send a mail with subject
1.34 + prefixed with "[CT_NG]" with to following destinations:
1.35 + TO: yann.morin.1998 (at) anciens.enib.fr
1.36 + CC: crossgcc (at) sourceware.org
1.37 +
1.38 +Sending patches
1.39 +---------------
1.40 +
1.41 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
1.42
1.43 -If you need to send a bug report or a patch, please send a mail with subject
1.44 -prefixed with "[CT_NG]" to the following destinations:
1.45 - TO: yann.morin.1998 (at) anciens.enib.fr
1.46 - CC: crossgcc (at) sourceware.org
1.47 -
1.48 Patches should come with the appropriate SoB line. A SoB line is typically
1.49 -something like:
1.50 - Signed-off-by: John DOE <john.doe@somewhere.net>
1.51 + something like:
1.52 + Signed-off-by: John DOE <john.doe@somewhere.net>
1.53
1.54 The SoB line is clearly described in Documentation/SubmittingPatches , section
1.55 12, of your favourite Linux kernel source tree.
1.56
1.57 +CREDITS /
1.58 +_______/
1.59 +
1.60 The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
1.61
1.62 +KNOWN ISSUES /
1.63 +____________/
1.64 +
1.65 The list of known issues is listed in docs/known-issues.txt.
1.66
1.67 Aloha!