From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 1/2] cr-daily-branch: Begin to support other reasons for forcing a baseline.
Date: Fri, 24 Jul 2015 18:05:24 +0100 [thread overview]
Message-ID: <21938.28756.181571.345965@mariner.uk.xensource.com> (raw)
In-Reply-To: <1436775392-14815-1-git-send-email-ian.campbell@citrix.com>
Ian Campbell writes ("[PATCH OSSTEST 1/2] cr-daily-branch: Begin to support other reasons for forcing a baseline."):
> By converting the current boolean $force_baseline into a keyword
> indicating the reason.
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
But I won't push this with my current batch.
Ian.
prev parent reply other threads:[~2015-07-24 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 8:16 [PATCH OSSTEST 1/2] cr-daily-branch: Begin to support other reasons for forcing a baseline Ian Campbell
2015-07-24 17:05 ` Ian Jackson [this message]
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=21938.28756.181571.345965@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 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).