From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>,
Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] travis: add IRC notifications
Date: Mon, 22 Feb 2016 17:08:19 +0000 [thread overview]
Message-ID: <56CB4083.2040707@citrix.com> (raw)
In-Reply-To: <22219.16428.592970.353449@mariner.uk.xensource.com>
On 22/02/16 17:06, Ian Jackson wrote:
> Doug Goldstein writes ("[PATCH] travis: add IRC notifications"):
>> This will cause failed builds and when the build flips back to success
>> to be reported to #xentest on FreeNode. The syntax of the message will
>> be:
>> <travis-ci> xen-project/xen#BUILDID (BRANCH - REVISION : COMMITTER)
>> <travis-ci> Change view :
>> https://github.com/xen-project/xen/compare/RANGE
>> <travis-ci> Build details :
>> https://travis-ci.org/xen-project/xen/builds/BUILDID
> I would like to give a little while for the community to comment on
> whether this is what they want. Personally I think it's a reasonable
> use of #xentest.
+1
~Andrew
next prev parent reply other threads:[~2016-02-22 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 15:13 [PATCH] travis: add IRC notifications Doug Goldstein
2016-02-22 17:06 ` Ian Jackson
2016-02-22 17:08 ` Andrew Cooper [this message]
2016-02-22 18:34 ` Doug Goldstein
2016-02-22 18:39 ` Lars Kurth
2016-02-22 19:03 ` Konrad Rzeszutek Wilk
2016-02-23 9:33 ` George Dunlap
2016-02-29 21:10 ` Doug Goldstein
2016-02-29 21:56 ` Konrad Rzeszutek Wilk
2016-03-01 18:10 ` Ian Jackson
2016-03-01 9:36 ` George Dunlap
2016-03-01 18:11 ` 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=56CB4083.2040707@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=lars.kurth.xen@gmail.com \
--cc=tim@xen.org \
--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).