summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEdwin Kempin <edwin.kempin@sap.com>2013-09-02 15:46:23 +0200
committerEdwin Kempin <edwin.kempin@sap.com>2013-09-02 15:46:23 +0200
commitf9f46bdca706bf24dc03f6ed3cf712778a9180fd (patch)
treea1a69fe3375dc10ed3347e3c89ecf84084673fad
parentbae9e58ddd68992473307787fb01e022f5969fee (diff)
Fix example for 'test-submit rule' in Prolog cookbook
Since commit b1f730b89458d9d094bc93f3d328ad744c39bbb5 it is 'test-submit rule' and not anymore 'test-submit-rule'. Change-Id: I4c32893afa1410af5347a8b659c5811aac218f63 Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
-rw-r--r--Documentation/prolog-cookbook.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/prolog-cookbook.txt b/Documentation/prolog-cookbook.txt
index 7912cf26a1..170d11a76a 100644
--- a/Documentation/prolog-cookbook.txt
+++ b/Documentation/prolog-cookbook.txt
@@ -303,11 +303,11 @@ Testing submit rules
The prolog environment running the `submit_rule` is loaded with state describing the
change that is being evaluated. The easiest way to load this state is to test your
`submit_rule` against a real change on a running gerrit instance. The command
-link:cmd-test-submit-rule.html[test-submit-rule] loads a specific change and executes
+link:cmd-test-submit-rule.html[test-submit rule] loads a specific change and executes
the `submit_rule`. It optionally reads the rule from from `stdin` to facilitate easy testing.
====
- cat rules.pl | ssh gerrit_srv gerrit test-submit-rule I45e080b105a50a625cc8e1fb5b357c0bfabe6d68 -s
+ cat rules.pl | ssh gerrit_srv gerrit test-submit rule I45e080b105a50a625cc8e1fb5b357c0bfabe6d68 -s
====
Prolog vs Gerrit plugin for project specific submit rules