# 
# patch "ChangeLog"
#  from [d3067d5bdea3712d1524711d7681b7621e4c234c]
#    to [28c6d73e3a0ba41687853781943609ea36144f8c]
# 
# patch "monotone.texi"
#  from [6af8010a77694d7c0f63a0a457c805cdc3729754]
#    to [c45e4e89f9f1108194a4f72c3d8d3344718d60f8]
# 
--- ChangeLog
+++ ChangeLog
@@ -1,5 +1,10 @@
 2005-07-05  Nathaniel Smith  <address@hidden>
-	
+
+	* monotone.texi (Database): Note that db kill_rev_locally also
+	will trigger "unreferenced manifest" warnings from db check.
+
+2005-07-05  Nathaniel Smith  <address@hidden>
+
 	* NEWS: Oops, 'automate select' was in 0.19 after all.
 
 2005-07-05  Nathaniel Smith  <address@hidden>
--- monotone.texi
+++ monotone.texi
@@ -4280,9 +4280,10 @@
 that exist in the database but are not referenced by their @sc{sha1}
 hash from any existing revision.  In itself, this only indicates some
 wasted space, and is not a problem; it's possible it could arise under
-normal use (for instance, in some strange corner cases following an
-incomplete netsync).  It could also arise, though, as a symptom of some
-other more serious problem.
+normal use (for instance, if you have run @command{db kill_rev_locally},
+or in some strange-but-harmless corner cases following an incomplete
+netsync).  It could also arise, though, as a symptom of some other more
+serious problem.
 
 @item incomplete manifests
 that exist in the database but contain references to files that do not