[Xen-devel] [OSSTEST PATCH 1/2] cs-adjust-flight: Correct pseudo-BNF synopsys for runvar-build-set

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

In 497b2c6c933d13a05b01c6a654ce470be16dd78a
  cs-adjust-flight: Rework runvar-build-set new value handling
the interpretation of this parameter was changed completely, but the
synopsis was not updated and thus became wrong.

Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
---
 cs-adjust-flight | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/cs-adjust-flight b/cs-adjust-flight
index f443cfd..afb81cb 100755
--- a/cs-adjust-flight
+++ b/cs-adjust-flight
@@ -14,7 +14,7 @@
 #   runvar-del <job-spec> <var-spec>
 #   runvar-change <job-spec> <var-spec> <old-value> <new-value>
 #   runvar-perlop <job-spec> <var-spec> <perl-expr>
-#   runvar-build-set <job-spec> <var-spec> <old-value> <flight>[.<job>]
+#   runvar-build-set <job-spec> <var-spec> <old-meaning> <new-value>|<flight>.
 #   recipe-set <job-spec> <new-value>
 #   intended-blessing <intended-blessing>
 #   branch-set <new-branch>
@@ -29,9 +29,10 @@
 #
 # runvar-build-set  always only affects runvars m/buildjob$/
 #                    and may be further limited by <var-spec>;
-#                   and, <old-value> is matched against a value
-#                    containing the being-manipulated flight name
-#                    even if the actual runvar value omits it
+#                   and, <old-meaning> is the old value but matches
+#                    against values containing the being-manipulated
+#                    flight name even if the actual runvar values
+#                    omits it
 #                   and, if <new-value> ends in ., it is
 #                    completed with the <old-value>'s job name
 #
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel