From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH] cs-adjust-flight: Allow runvar-build-set new value to be just "."
Date: Fri, 6 Jul 2018 14:49:56 +0100 [thread overview]
Message-ID: <1530884996-31406-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
This is useful because if you say new: for the flight to be adjusted,
you don't have the flight number.
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
cs-adjust-flight | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/cs-adjust-flight b/cs-adjust-flight
index 4f036f4..ee1d917 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-meaning> <new-value>|<flight>.
+# 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>
@@ -35,6 +35,7 @@
# omits it
# and, if <new-value> ends in ., it is
# completed with the <old-value>'s job name
+# (and if it is just `.' it means just that job name)
#
# <dst-flight>:
# <flight>
@@ -369,7 +370,8 @@ sub change__runvar_build_set {
return unless $oldvalok_fn->("$oldflt.$oldjob");
$matches++;
- my $newval = $specval =~ m/\.$/ ? "$specval$oldjob": $specval;
+ my $newval = $specval eq '.' ? $oldjob :
+ $specval =~ m/\.$/ ? "$specval$oldjob": $specval;
runvar_set($job, $name, $newval, " (modified from \`$oldval')")
if $newval ne $oldval;
}, 'IGNORE');
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-07-06 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1530884996-31406-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).