All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST] ap-fetch-version-old: Fix qemu branch handling after mergin of qemu trees
Date: Fri, 23 Oct 2015 11:23:38 +0100	[thread overview]
Message-ID: <22058.2730.735937.499912@mariner.uk.xensource.com> (raw)
In-Reply-To: <1445594806-23505-1-git-send-email-ian.campbell@citrix.com>

Ian Campbell writes ("[PATCH OSSTEST] ap-fetch-version-old: Fix qemu branch handling after mergin of qemu trees"):
> ap-fetch-version-old should always reference the output gate, but
> 99e92a6b3991 "Switch to merged qemu-xen{,-traditional}.git trees"
> switched it to use TREE_QEMU_UPSTREAM directly, which can be
> overridden by cr-daily-branch. This broke at least when
> OSSTEST_BASELINES_ONLY=y since "cr-daily-branch qemu-mainline" ends up looking
> for an "upstream-tested" branch in the qemu.org git tree, when it should be
> looking at our output tree on xenbits.
> 
> Follow pattern of TREE_LINUX and set BASE_TREE_QEMU_UPSTREAM to the
> output gate and then conditionally set TREE_QEMU_UPSTREAM to the
> BASE_TREE if it is not already set. Switch ap-fetch-version-old to use
> BASE_TREE.
...
> +if [ "x${TREE_QEMU_UPSTREAM}" ]; then
> +	: ${TREE_QEMU_UPSTREAM:=${BASE_TREE_QEMU_UPSTREAM}}
> +fi

${FOO:=BAR} sets FOO iff FOO is unset or empty, so there is no need
for the if.  The place you cribbed this from also has to set a
variable for the refname.

Everthing else about this is fine.  Thanks for the in-person explanation.

Ian.

  reply	other threads:[~2015-10-23 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 10:06 [PATCH OSSTEST] ap-fetch-version-old: Fix qemu branch handling after mergin of qemu trees Ian Campbell
2015-10-23 10:23 ` Ian Jackson [this message]
2015-10-23 10:33   ` Ian Campbell

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=22058.2730.735937.499912@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=ian.campbell@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 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.