# HG changeset patch
# User jbe
# Date 1405035865 -7200
# Node ID e3dd2c3629dbdb5bc2af24beebc6429e80c765a9
# Parent  692729de151ad7c4fbcb10bf51df908cf3586e6a
Added missing information on "lf_update_issue_order" to README file

diff -r 692729de151a -r e3dd2c3629db README
--- a/README	Thu Jul 10 01:32:20 2014 +0200
+++ b/README	Fri Jul 11 01:44:25 2014 +0200
@@ -9,7 +9,8 @@
 Compile lf_update binary:
 $ make
 
-Ensure that "lf_update dbname=liquid_feedback" and
+Ensure that "lf_update dbname=liquid_feedback",
+"lf_update_issue_order dbname=liquid_feedback", and
 "lf_update_suggestion_order dbname=liquid_feedback" are called
 regularly! It is required to run these commands regularly
 (i.e. every 5 minutes via cron) to update cached supporter counts,
@@ -21,11 +22,12 @@
 It is possible to run these two commands in parallel, if a setup
 requires splitting the load to multiple processor cores. In other
 cases it is recommended to run "lf_update" first, and then
-"lf_update_suggestion_order".
+"lf_update_issue_order" and "lf_update_suggestion_order".
 
 On successful run, these commands will not produce any output
-and exit with code 0. The command "lf_update_suggestion_order" may
-be called with a first argument of "-v" to print log output.
+and exit with code 0. The commands "lf_update_issue_order" and
+"lf_update_suggestion_order" may be called with a first argument
+of "-v" to print log output.
 
 NOTE: When writing to the database, some INSERTs must be executed
       within the same transaction, e.g. issues can't exist without