Yann E. MORIN" 43850b301c docs: add a status for know issues ... As time passes, a known issues can be no longer applicable (because the component has been fixed, or a workaround ahs been added in the crosstool-NG scripts/config...). Some may also be unconfirmed, with no way to easily trigger the error, or applies to old versions of components... Add a status for every known issues. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>		2011-04-07 19:21:15 +02:00
..
0 - Table of content.txt	docs: add known issues summary in the ToC	2011-04-07 19:13:09 +02:00
1 - Introduction.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
2 - Installing crosstool-NG.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
3 - Configuring a toolchain.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
4 - Building the toolchain.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
5 - Using the toolchain.txt	config: add an option to name the sysroot directory	2011-01-25 20:31:16 +01:00
6 - Toolchain types.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
7 - Contributing to crosstool-NG.txt	docs: move the Mercurial tutorial to the tutorials section	2010-08-14 20:26:23 +02:00
8 - Internals.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
9 - How is a toolchain constructed.txt	docs: rename chapter 9	2011-02-27 15:27:54 +01:00
A - Credits.txt	docs: split into multiple files	2010-08-14 16:37:11 +02:00
B - Known issues.txt	docs: add a status for know issues	2011-04-07 19:21:15 +02:00
C - Misc. tutorials.txt	docs: move the Mercurial tutorial to the tutorials section	2010-08-14 20:26:23 +02:00
ct-ng.1.in	docs: overview.txt is gone, point to the new documentation	2010-12-22 00:34:56 +01:00