From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 3/3] .shippable.yml: new CI provider
Date: Wed, 15 Feb 2017 08:51:42 +0800 [thread overview]
Message-ID: <20170215005142.GA26331@lemon.lan> (raw)
In-Reply-To: <87bmu4vk8v.fsf@linaro.org>
On Tue, 02/14 15:56, Alex Bennée wrote:
> > May I propose we merge 'docker testing' section of MAINTAINERS into 'build and
> > test automation' section? I don't know as much about travis (and shippable) but
> > I'm totally fine if you want to have docker tests under your umbrella, and
> > it seems a logical step judging from their names.
>
> So:
>
> Build and test automation
> -------------------------
> M: Alex Bennée <alex.bennee@linaro.org>
> M: Fam Zheng <famz@redhat.com>
> L: qemu-devel@nongnu.org
> S: Maintained
> F: .travis.yml
> F: .shippable.yml
> F: tests/docker/
Yes, looks good. Please include a patch in v4.
>
> Or did you want to drop out of the review cycle and concentrate on patchew?
I would still keep my eyes on tests/docker/, the intent is just for being more
compact on MAINTAINERS.
Fam
prev parent reply other threads:[~2017-02-15 0:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:07 [Qemu-devel] [PATCH v3 0/3] Docker cross-compile targets and user build support Alex Bennée
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 1/3] tests/docker: add basic user mapping support Alex Bennée
2017-02-14 14:22 ` Fam Zheng
2017-02-14 15:11 ` Alex Bennée
2017-02-14 15:20 ` Fam Zheng
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 2/3] new: debian docker targets for cross-compiling Alex Bennée
2017-02-14 14:00 ` Fam Zheng
2017-02-14 14:27 ` Fam Zheng
2017-02-14 15:10 ` Alex Bennée
2017-02-14 14:30 ` Peter Maydell
2017-02-14 15:09 ` Alex Bennée
2017-02-14 15:18 ` Fam Zheng
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 3/3] .shippable.yml: new CI provider Alex Bennée
2017-02-14 14:11 ` Fam Zheng
2017-02-14 15:56 ` Alex Bennée
2017-02-15 0:51 ` Fam Zheng [this message]
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=20170215005142.GA26331@lemon.lan \
--to=famz@redhat.com \
--cc=alex.bennee@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 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.