From: Doug Goldstein <cardoe@cardoe.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@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 12:34:17 -0600 [thread overview]
Message-ID: <56CB54A9.6080902@cardoe.com> (raw)
In-Reply-To: <22219.16428.592970.353449@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 868 bytes --]
On 2/22/16 11:06 AM, 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.
>
> I'm tempted to suggest that osstest reports should go there too :-).
>
> CCing Lars.
>
> Ian.
>
I'd like to see osstest reports go there as well.
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-22 18:34 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
2016-02-22 18:34 ` Doug Goldstein [this message]
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=56CB54A9.6080902@cardoe.com \
--to=cardoe@cardoe.com \
--cc=Ian.Jackson@eu.citrix.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 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.