From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH 3/8] emails: honour OSSTEST_EMAIL_SUBJECT_PREFIX
Date: Fri, 27 Feb 2015 09:31:13 +0000 [thread overview]
Message-ID: <1425029473.14641.111.camel@citrix.com> (raw)
In-Reply-To: <21743.23437.578256.663822@mariner.uk.xensource.com>
On Thu, 2015-02-26 at 17:44 +0000, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 3/8] emails: honour OSSTEST_EMAIL_SUBJECT_PREFIX"):
> > On Wed, 2015-02-25 at 13:01 +0000, Ian Jackson wrote:
> > > This is prefixed before the other computed prefixes. It makes it
> > > easier to distinguish an adhoc cr-daily-branch test runs for a real
> > > branch.
> >
> > Do they not already get "adhoc" in the $subject? i.e. my commissioning
> > runs for the new arm create (following README.dev procedure) resulted in
> > mails with:
> >
> > [adhoc test] 34418: trouble: blocked/broken/fail/pass
> >
> > (IOW it seems $branch is replaced by adhoc somewhere along the say)
>
> That happens if you use mg-execute-flight. If you let cr-daily-branch
> run the flight for you, it uses the standard email stuff.
Ah, OK, I didn't realise there was a difference.
So Ack to this and the next patch which I didn't ack for similar
reasons. (I think that makes the whole series acked, FWIW)
>
> Ian.
next prev parent reply other threads:[~2015-02-27 9:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 13:01 [OSSTEST PATCH 0/8] improvements related to adhoc testing Ian Jackson
2015-02-25 13:01 ` [OSSTEST PATCH 1/8] emails: cr*: Defer setting of OSSTEST_EMAIL_HEADER Ian Jackson
2015-02-25 13:25 ` Ian Campbell
2015-02-25 13:01 ` [OSSTEST PATCH 2/8] emails: branch-settings.osstest: Permit caller to specify OSSTEST_EMAIL_HEADER Ian Jackson
2015-02-25 13:25 ` Ian Campbell
2015-02-25 13:01 ` [OSSTEST PATCH 3/8] emails: honour OSSTEST_EMAIL_SUBJECT_PREFIX Ian Jackson
2015-02-25 13:24 ` Ian Campbell
2015-02-26 17:44 ` Ian Jackson
2015-02-27 9:31 ` Ian Campbell [this message]
2015-02-25 13:01 ` [OSSTEST PATCH 4/8] emails: Set OSSTEST_EMAIL_SUBJECT_PREFIX if not --real Ian Jackson
2015-02-25 13:01 ` [OSSTEST PATCH 5/8] standalone: Always set OSSTEST_NO_BASELINE Ian Jackson
2015-02-25 13:26 ` Ian Campbell
2015-02-26 17:49 ` Ian Jackson
2015-02-25 13:01 ` [OSSTEST PATCH 6/8] standalone: Always pass OLD_REVISION=NONE to cr-daily-branch Ian Jackson
2015-02-25 13:28 ` Ian Campbell
2015-02-25 13:01 ` [OSSTEST PATCH 7/8] ap-fetch-version-old: Do not honour OSSTEST_USE_HEAD Ian Jackson
2015-02-25 13:28 ` Ian Campbell
2015-02-25 13:01 ` [OSSTEST PATCH 8/8] ap-fetch-version: Use osstest's home to find master tree Ian Jackson
2015-02-25 13:29 ` Ian Campbell
2015-02-26 17:52 ` 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=1425029473.14641.111.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=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.