From: Vinod Koul <vinod.koul@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Fri, 29 Jul 2016 21:56:07 +0530 [thread overview]
Message-ID: <20160729162607.GM9681@localhost> (raw)
In-Reply-To: <20160728223845.GI16852@dtor-ws>
On Thu, Jul 28, 2016 at 03:38:45PM -0700, Dmitry Torokhov wrote:
> > I know that such a feature exists, but I'm not sure all developers would
> > appreciate the additional e-mail traffic. That's why I proposed a status page
> > that could be polled when needed.
>
> I for one really appreciate that I do not need to poll anything and
> instead I am notified when stuff that I pushed passed/failed some tests.
> So, even if there are status pages and what's not, please do keep opt-in
> email notifications.
Same here, I do look for mail from Fengguang after I have pushed stuff up.
Said that, if we have a lookup interface, I won't mind at all, given that
sometimes latencies vary, so knowing the latest status, branch and commit
built would help.
Also on mailing list tests, I would really like a status page. Right now it
only reports errors, which is great. But I won't know if tests were run or
not. It happened on one of our lists recently
> Thanks Fengguang!
Absolutely, this bot has been a great service to kernel community.
Thanks
--
~Vinod
next prev parent reply other threads:[~2016-07-29 16:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 19:01 Luis R. Rodriguez
2016-07-25 20:23 ` Alexandre Belloni
2016-07-26 3:10 ` Vinod Koul
2016-07-26 8:16 ` Laurent Pinchart
2016-07-26 8:56 ` Vinod Koul
2016-07-28 13:20 ` Fengguang Wu
2016-07-27 14:50 ` Fengguang Wu
2016-07-28 16:15 ` Laurent Pinchart
2016-07-28 20:53 ` Fengguang Wu
2016-07-28 20:59 ` Laurent Pinchart
2016-07-28 22:38 ` Dmitry Torokhov
2016-07-29 16:26 ` Vinod Koul [this message]
2016-07-28 23:07 ` Fengguang Wu
2016-07-28 23:33 ` Luis R. Rodriguez
2016-07-29 0:09 ` Fengguang Wu
2016-07-29 15:12 ` Bjorn Helgaas
2016-07-30 17:05 ` Luis R. Rodriguez
2016-07-30 17:24 ` Guenter Roeck
2016-07-31 6:35 ` Fengguang Wu
2016-07-31 17:32 ` Vinod Koul
2016-08-01 13:35 ` Fengguang Wu
2016-07-28 23:38 ` Jiri Kosina
2016-07-31 11:16 ` Fengguang Wu
2016-07-29 2:00 ` Steven Rostedt
2016-07-29 2:26 ` Fengguang Wu
2016-07-27 14:41 ` Fengguang Wu
2016-07-28 17:15 ` Guenter Roeck
2016-07-28 17:21 ` Dmitry Vyukov
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=20160729162607.GM9681@localhost \
--to=vinod.koul@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.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