xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH OSSTEST 1/5] cs-adjust-flight: `branch' command ought to be `branch-set'
Date: Mon, 5 Oct 2015 15:35:04 +0100	[thread overview]
Message-ID: <1444055708-15836-1-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1444055694.5302.9.camel@citrix.com>

Also add a doc string and since this op is not a change adjust the doc
comment accordingly.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
v3: New patch.
---
 cs-adjust-flight | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/cs-adjust-flight b/cs-adjust-flight
index 834e2c8..a94ed5f 100755
--- a/cs-adjust-flight
+++ b/cs-adjust-flight
@@ -3,9 +3,9 @@
 # destination flight must already exist
 #
 # args:
-#   <dst-flight> [<change> ...]
+#   <dst-flight> [<op> ...]
 #
-# <change>:
+# <op>:
 #   copy <flight>
 #   copy-jobs <flight> <job-spec>
 #   jobs-list <job-spec>
@@ -16,6 +16,7 @@
 #   runvar-perlop <job-spec> <var-spec> <perl-expr>
 #   recipe-set <job-spec> <new-value>
 #   intended-blessing <intended-blessing>
+#   branch-set <new-branch>
 #
 # <foo-spec>:
 #   <foo-name>
@@ -330,7 +331,7 @@ sub change__intended_blessing {
     verbose "$dstflight blessing set to $blessing\n";
 }
 
-sub change__branch {
+sub change__branch_set {
     die unless @changes >= 1;
     my $branch = shift @changes;
 
-- 
2.5.3

  reply	other threads:[~2015-10-05 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 14:34 [PATCH OSSTEST v3 0/5] Misc standalone wrapper improvements Ian Campbell
2015-10-05 14:35 ` Ian Campbell [this message]
2015-10-06 14:41   ` [PATCH OSSTEST 1/5] cs-adjust-flight: `branch' command ought to be `branch-set' Ian Jackson
2015-10-05 14:35 ` [PATCH OSSTEST 2/5] cs-adjust-flight: Add job-status to report job stats Ian Campbell
2015-10-06 14:44   ` Ian Jackson
2015-10-06 14:56     ` Ian Campbell
2015-10-05 14:35 ` [PATCH OSSTEST 3/5] standalone: Check job status at end of run-job Ian Campbell
2015-10-05 14:35 ` [PATCH OSSTEST 4/5] standalone: Make it possible to pass options to run-test Ian Campbell
2015-10-06 14:46   ` Ian Jackson
2015-10-06 14:59     ` Ian Campbell
2015-10-06 15:24       ` Ian Jackson
2015-10-06 15:35       ` Ian Campbell
2015-10-06 15:37         ` Ian Jackson
2015-10-05 14:35 ` [PATCH OSSTEST 5/5] standalone: Use fail() from mgi-common in most places Ian Campbell
2015-10-06 14:46   ` Ian Jackson

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=1444055708-15836-1-git-send-email-ian.campbell@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).