Started to rescind the name "skin", replacing it with "tool". Did this in all
the places that normal users will see:
- command line: --tool=foo (although --skin=foo still works)
- docs: removed all traces (included renaming coregrind_skins.html to
coregrind_tools.html)
- in the usage messages
- in error messages
Also did in in some places that I judged were unlikely to cause clashes with
existing workspaces:
- in the header comments of many files (eg. "This file is part of Memcheck, a
Valgrind tool for...")
- in the regtests script
- in the .supp files
- in AUTHORS
- in README_MISSING_SYSCALL_OR_IOCTL
Also update the AUTHORS file to mention Jeremy.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2027 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/none/docs/nl_main.html b/none/docs/nl_main.html
index c72ba6a..fc6996e 100644
--- a/none/docs/nl_main.html
+++ b/none/docs/nl_main.html
@@ -35,21 +35,21 @@
<p>
Nulgrind is licensed under the GNU General Public License,
version 2<br>
-Nulgrind is a Valgrind skin that does not very much at all.
+Nulgrind is a Valgrind tool that does not very much at all.
</center>
<p>
<h2>1 Nulgrind</h2>
-Nulgrind is the minimal skin for Valgrind. It does no initialisation or
+Nulgrind is the minimal tool for Valgrind. It does no initialisation or
finalisation, and adds no instrumentation to the program's code. It is mainly
of use for Valgrind's developers for debugging and regression testing.
<p>
Nonetheless you can run programs with Nulgrind. They will run roughly 5-10
times more slowly than normal, for no useful effect. Note that you need to use
-the option <code>--skin=none</code> to run Nulgrind (ie. not
-<code>--skin=nulgrind</code>).
+the option <code>--tool=none</code> to run Nulgrind (ie. not
+<code>--tool=nulgrind</code>).
<hr width="100%">
</body>