Introduce the notion of a 'sample comment'.

- presence of the sample's reported.by file is now mandatory.
- when saving a sample, reporter name & URL are queried, to avoid operator forget about creating the reported.by file.
- when saving a sample, one can store a few-liner comment.
- when recalling a sample, the reporter name, URL and comment (if present) are printed.
- update the powerpc-e500v2-linux-gnuspe sample to include Nate's comment (from his original mail).
- update all samples that were missing the reported.by file.

/trunk/scripts/saveSample.sh | 46 35 11 0 ++++++++++++++++++------
/trunk/scripts/showSamples.sh | 12 6 6 0 +++---
/trunk/samples/powerpc-e500v2-linux-gnuspe/reported.by | 15 15 0 0 ++++++++
/trunk/samples/samples.mk | 22 17 5 0 +++++++++--
4 files changed, 73 insertions(+), 22 deletions(-)

This is the README for crosstool-NG

To get you started, just enter:

  ./configure --help

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/dokuwiki/projects/crosstool

If you need to send a bug report or a patch, please send a mail with subject

prefixed with "[CT_NG]" with the following destinations:

    TO: yann.morin.1998 (at) anciens.enib.fr

    CC: crossgcc (at) sourceware.org

The people that helped are listed in docs/CREDITS. Many thanks to them! :-)

The list of known issues is listed in docs/known-issues.txt.

Aloha!