From: Ian Jackson <ian.jackson@eu.citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [Xen-devel] [OSSTEST PATCH v2 4/8] mg-repro-setup: Do not imply that a --rebuild needs a +TREE
Date: Fri, 21 Jun 2019 15:22:54 +0100 [thread overview]
Message-ID: <20190621142258.1543-5-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <20190621142258.1543-1-ian.jackson@eu.citrix.com>
The +TREEs and other specifications are convolved.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
mg-repro-setup | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/mg-repro-setup b/mg-repro-setup
index 5a52e617..9a81c565 100755
--- a/mg-repro-setup
+++ b/mg-repro-setup
@@ -45,8 +45,7 @@ usage () { cat <<END
REBUILD is
--rebuild [-B<blessing>] [-r...]
- [.BUILDJOB | =BUILDJOBRUNVAR...]
- +TREE=URL#REVISION...
+ [.BUILDJOB | =BUILDJOBRUNVAR | +TREE=URL#REVISION ...]
Also use a different build. Specifically, use URL and REVISION
for certain builds which mention TREE and which are referenced
(directly) in the job JOB in EXAMPLE-FLIGHT. The affected builds
@@ -55,7 +54,7 @@ usage () { cat <<END
name is any of the BUILDJOB (in which case all references to that
job are adjusted). If no .BUILDJOB and no =BUILDJOBRUNVAR are
specified, then all jobs referred to from the example JOB
- which mention TREE are affected.
+ which mention a TREE are affected.
For example,
--rebuild =xenbuildjob \
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-06-21 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:22 [Xen-devel] [OSSTEST PATCH v2 0/8] mg-repro-* improvements Ian Jackson
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 1/8] mg-transient-task: New utility Ian Jackson
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 2/8] mg-transient-task: Put the ownd fd on a high fd, say, 114 Ian Jackson
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 3/8] mg-repro-setup: Do all builds in their own tasks, regardless Ian Jackson
2019-06-21 14:22 ` Ian Jackson [this message]
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 5/8] mg-repro-setup: Introduce `statictask' variable Ian Jackson
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 6/8] mg-repro-setup: New mode --autoalloc Ian Jackson
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 7/8] mg-repro-setup: actually accept --rebuild -rVAR=VALUE Ian Jackson
2019-06-21 14:22 ` [Xen-devel] [OSSTEST PATCH v2 8/8] mg-repro-setup: Do not wrongly reject multiple --rebuild 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=20190621142258.1543-5-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.