From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Fam Zheng <famz@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/21] Docker and shippable updates
Date: Mon, 10 Jul 2017 15:17:17 +0100 [thread overview]
Message-ID: <87r2xo9y1e.fsf@linaro.org> (raw)
In-Reply-To: <CAAdtpL7kaQSm_Kbn+DrD9Kkzj3JH47pM+-RxXYB=_fyEb+7NxQ@mail.gmail.com>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> On Thu, Jun 22, 2017 at 12:42 PM, Philippe Mathieu-Daudé
> <f4bug@amsat.org> wrote:
>> On Thu, Jun 22, 2017 at 12:13 PM, Alex Bennée <alex.bennee@linaro.org> wrote:
>>> Now we've been running shippable for a while is it worth turning on the
>>> IRC notifications?
>>
>> What about moving such bot/scripts notifications in another channel
>> like #QEMU-notifications?
>
> ping?
I'm in two minds so I suspect this is something that needs to be taken
to the users of #qemu.
>> It is often hard to follow 3 concurrent topics while the travis-ci bot
>> disrupts entering/broadcasting/leaving...
I find it useful as its somewhere I look at a lot. That said it is not
exactly a trial to sub to yet another IRC channel.
>> I'd also like to see here checkpatch/patchew stripped output, and
>> eventually gcov/gprof reports.
>> I don't think full patchew reports are useful in a mailbox.
I disagree. They could certainly be made terser but I think the general
workflow of posting automated testing reports to patch series is a
useful one.
--
Alex Bennée
next prev parent reply other threads:[~2017-07-10 14:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 14:47 [Qemu-devel] [PULL 00/21] Docker and shippable updates Alex Bennée
2017-06-21 14:47 ` [Qemu-devel] [PULL 01/21] docker: update qemu:debian base following stretch release Alex Bennée
2017-06-21 14:47 ` [Qemu-devel] [PULL 02/21] docker: let _copy_with_mkdir() sub_path argument be optional Alex Bennée
2017-06-21 14:47 ` [Qemu-devel] [PULL 03/21] docker: add --include-files argument to 'build' command Alex Bennée
2017-06-21 14:47 ` [Qemu-devel] [PULL 04/21] docker: rebuild image if 'extra files' checksum does not match Alex Bennée
2017-06-21 14:47 ` [Qemu-devel] [PULL 05/21] docker: install ca-certificates package in base image Alex Bennée
2017-06-21 14:47 ` [Qemu-devel] [PULL 06/21] docker: use better regex to generate deb-src entries Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 07/21] docker: use eatmydata, install common build packages in base image Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 08/21] docker: use eatmydata in debian armhf image Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 09/21] docker: use eatmydata in debian arm64 image Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 10/21] docker: add extra libs to armhf target to extend codebase coverage Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 11/21] docker: add extra libs to arm64 " Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 12/21] docker: add extra libs to s390x " Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 13/21] docker: add mipsel build target Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 14/21] shippable: use C locale to simplify console output Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 15/21] shippable: build using all available cpus Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 16/21] shippable: do not initialize submodules automatically Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 17/21] shippable: be verbose while building docker images Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 18/21] shippable: add armeb-linux-user target Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 19/21] shippable: add mipsel target Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 20/21] MAINTAINERS: add Shippable automation platform URL Alex Bennée
2017-06-21 14:48 ` [Qemu-devel] [PULL 21/21] MAINTAINERS: self-appoint me as reviewer in build/test automation Alex Bennée
2017-06-22 14:09 ` [Qemu-devel] [PULL 00/21] Docker and shippable updates Peter Maydell
2017-06-22 14:58 ` Philippe Mathieu-Daudé
2017-06-22 15:13 ` Alex Bennée
2017-06-22 15:42 ` Philippe Mathieu-Daudé
2017-07-10 12:04 ` Philippe Mathieu-Daudé
2017-07-10 14:17 ` Alex Bennée [this message]
2017-07-10 14:22 ` Peter Maydell
2017-07-12 12:17 ` Philippe Mathieu-Daudé
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=87r2xo9y1e.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).