Add 'fsck' to the documentation.

diff --git a/README b/README
index ce882d60664d104ffafcb058cc72a2c467aff679..c0f3d5ef450dee0e793635efae79a31c9124b6a9 100644 (file)
--- a/README
+++ b/README
@@ -81,6 +81,12 @@ it from the issue:
 
  $ cil extract decaf7ea --filename=mycore
 
+Finally, because the cil issue files reside on the filesystem in flat files,
+there needs to be a way to check the integrity of the issues, therefore you can
+run this to do checks regarding the whole issue list:
+
+ $ cil fsck
+
 That's it for now. As you can see, if you've played with any kind of bug/issue
 tracker before, 'cil' is straightforward.
 

diff --git a/bin/cil b/bin/cil
index 9e9604b4caead3f28e92d5530b680bfdb3c49c46..c509717e341d0bd388727fa9b25549c78a1da6c1 100755 (executable)
--- a/bin/cil
+++ b/bin/cil
@@ -776,6 +776,7 @@ Commands:
    comment ISSUE
    attach  ISSUE FILENAME
    extract ATTACHMENT [--filename=FILENAME]
+   fsck
 
 See <http://kapiti.geek.nz/software/cil.html> for further information.
 Report bugs to <andychilton -at- gmail -dot- com>.
@@ -811,6 +812,8 @@ cil - the command-line issue list
     $ cil extract decaf7ea
     $ cil extract decaf7ea --filename=other_filename.txt
 
+    $ cil fsck
+
 =head1 DESCRIPTION
 
 Cil is a small but useful command-line issue list. It saves issues, comments