Changes To fossil ls
Not logged in
@@ -18,11 +18,11 @@
 it's the status as <b>fossil</b> sees it and has nothing to do with
 filesystem status.  If you're new to source-management/version-control
 systems, you'll probably get bit by this concept-bug at least once.
 
 To really see the difference, issue an <code>ls</code> before and after doing
-a <code>commit</code>.  Before, the status of files may be any of the three,
+a <a href="wiki?name=fossil+commit"><code>commit</code></a>.  Before, the status of files may be any of the three,
 but after <code>commit</code>ting changes the status will be UNCHANGED "across
 the board."
 
 By way of example, here's what I see if I <code>fossil ls</code> in the
 directory where I have checked out my testing repository:
@@ -40,7 +40,11 @@
 </pre></nowiki>
 
 The <code>ls</code> command is almost, but not quite entirely, the exact
 opposite of the
 <a href="wiki?name=fossil+extra"><code>extra</code> command</a>.
+
+Notes:
+  *  There are more states for a file to be in than those listed, including MISSING, EDITED, RENAMED and a couple of others.
+  *  If you come from the <b>Windows</b> world, it will help to know that 'ls' is the usually <b>unix</b> command for listing a directory.
 
 See also: [fossil add], [fossil rm], [fossil extra], [fossil commit], <a href="doc/tip/www/concepts.wiki">Fossil concepts</a>, [Reference]