# 
# patch "ChangeLog"
#  from [e982eddbf888a6572202ccfc1ff02f5da407abc8]
#    to [ba42af7fe0f562b05ef75b1b7e47176e2e1f6e59]
# 
# patch "monotone.texi"
#  from [86788028f6e7a05e423af34635bd568f6966eb40]
#    to [61824db5177a5debdfc466f83966c2278c578375]
# 
--- ChangeLog
+++ ChangeLog
@@ -1,3 +1,7 @@
+2005-04-21 Sebastian Spaeth <address@hidden>
+
+	* monotone.texi: add command reference docs about kill_rev_locally
+	
 2005-04-20 Sebastian Spaeth <address@hidden>
 	* automate.cc: fix typo, add sanity check to avoid empty r_id's
 	bein passed in. The automate version was bumped to 0.2 due to
--- monotone.texi
+++ monotone.texi
@@ -4200,6 +4200,18 @@
 This command also verifies that the @sc{sha1} of every file, manifest,
 and revision is correct.
 
address@hidden monotone db kill_rev_locally @var{rev1}
+
+This will simply delete a revision with revision id @var{rev1} from your
+local database.  If you already synchronized with another database this
+command is senseless, as it will come back to you.  It might leave some
+unreferenced 'manifest ids' and 'file deltas' in your database which is
+non-fatal but annoying.  Generally, this is not the preferred way of
+doing things, you might want to use @var{disapprove} to undo changes
+instead. @var{kill_rev_locally} basically belongs in the category of
+useful but
address@hidden''-category.
+
 @item monotone db execute @var{sql-statement}
 
 This is a debugging command which executes @var{sql-statement} against