Add sections to the README

1 files changed, 36 insertions, 7 deletions

diff --git a/README b/README
index ac7ef784..b90d07ec 100644
--- a/README
+++ b/README
@@ -1,5 +1,19 @@
 This is the README for crosstool-NG
 
+TABLE OF CONTENT /
+________________/
+
+  - GETTING STARTED
+  - PARTICIPATING
+    - Sending a bug report
+    - Sending patches
+  - CREDITS
+  - KNOWN ISSUES
+
+
+GETTING STARTED /
+_______________/
+
 To get you started, just enter:
   ./configure --help
 
@@ -8,22 +22,37 @@ You can find a (terse and WIP) documentation in docs/overview.txt.
 You can also point your browser to
   http://ymorin.is-a-geek.org/projects/crosstool
 
-If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
+PARTICIPATING /
+_____________/
+
+Sending a bug report
+--------------------
 
-If you need to send a bug report or a patch, please send a mail with subject
-prefixed with "[CT_NG]" to the following destinations:
-    TO: yann.morin.1998 (at) anciens.enib.fr
-    CC: crossgcc (at) sourceware.org
+If you need to send a bug report, please send a mail with subject
+ prefixed with "[CT_NG]" with to following destinations:
+     TO: yann.morin.1998 (at) anciens.enib.fr
+     CC: crossgcc (at) sourceware.org
+
+Sending patches
+---------------
+
+If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
 
 Patches should come with the appropriate SoB line. A SoB line is typically
-something like:
-  Signed-off-by: John DOE <john.doe@somewhere.net>
+ something like:
+   Signed-off-by: John DOE <john.doe@somewhere.net>
 
 The SoB line is clearly described in Documentation/SubmittingPatches , section
 12, of your favourite Linux kernel source tree.
 
+CREDITS /
+_______/
+
 The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
 
+KNOWN ISSUES /
+____________/
+
 The list of known issues is listed in docs/known-issues.txt.
 
 Aloha!