From: Chris Metcalf <cdmetcalf@comcast•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>, linux-next@vger•kernel.org
Subject: kisskb.ellerman.id.au email notifications?
Date: Wed, 06 Jun 2012 11:54:21 -0400 [thread overview]
Message-ID: <4FCF7D2D.6030809@comcast.net> (raw)
Stephen -
I noticed when I merged up to 3.4-rc1 that there were some build issues
with tilegx (I've pushed the fixes to my tree for linux-next). Googling
around a little and referring to some earlier discussions, I realized that
http://kisskb.ellerman.id.au tracks the build successes and failures for
various branches and architectures, including tilegx on linux-next.
My question is whether there's a way to get email notification when a
particular build does fail. I'd like to know when things break the tilegx
build, in between the times when I actually sync up and check it myself.
Is there a mechanism for that, or should I stick with periodically checking
the website manually - which of course is much better than nothing! :-)
Thanks!
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next reply other threads:[~2012-06-06 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 15:54 Chris Metcalf [this message]
2012-06-06 22:26 ` kisskb.ellerman.id.au email notifications? Stephen Rothwell
2012-06-06 22:44 ` Chris Metcalf
2012-06-06 23:17 ` Stephen Warren
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=4FCF7D2D.6030809@comcast.net \
--to=cdmetcalf@comcast$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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