From: Kevin Traynor <ktraynor@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: stable@dpdk.org, msantana@redhat.com
Subject: Re: [dpdk-stable] [PATCH 18.11 0/3] Travis for 18.11 stable branch
Date: Tue, 14 May 2019 13:57:55 +0100 [thread overview]
Message-ID: <4eba40b4-29e4-3c07-050e-46b410bc8010@redhat.com> (raw)
In-Reply-To: <f7ty33eo0ws.fsf@dhcp-25.97.bos.redhat.com>
On 10/05/2019 15:10, Aaron Conole wrote:
> Kevin Traynor <ktraynor@redhat.com> writes:
>
>> Travis is convenient way of build testing. Backport Travis
>> integration to 18.11 branch.
>>
>> One later path fix on master (76f8486e16) dropped as n/a for 18.11.
>>
>> Aaron Conole (2):
>> ci: enable ccache in Travis
>> ci: add a distinguisher to the extra Travis builds
>>
>> Michael Santana (1):
>> ci: introduce Travis builds for GitHub repositories
>>
>> .ci/linux-build.sh | 24 +++++++
>> .ci/linux-setup.sh | 3 +
>> .travis.yml | 98 +++++++++++++++++++++++++++++
>> MAINTAINERS | 6 ++
>> doc/guides/contributing/patches.rst | 4 ++
>> 5 files changed, 135 insertions(+)
>> create mode 100755 .ci/linux-build.sh
>> create mode 100755 .ci/linux-setup.sh
>> create mode 100644 .travis.yml
>
> For the series:
>
> Acked-by: Aaron Conole <aconole@redhat.com>
>
Thanks Aaron and Micheal, pushed to dpdk-stable:18.11
prev parent reply other threads:[~2019-05-14 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 12:43 Kevin Traynor
2019-05-10 12:43 ` [dpdk-stable] [PATCH 18.11 1/3] ci: introduce Travis builds for GitHub repositories Kevin Traynor
2019-05-10 12:43 ` [dpdk-stable] [PATCH 18.11 2/3] ci: enable ccache in Travis Kevin Traynor
2019-05-10 12:43 ` [dpdk-stable] [PATCH 18.11 3/3] ci: add a distinguisher to the extra Travis builds Kevin Traynor
2019-05-10 14:10 ` [dpdk-stable] [PATCH 18.11 0/3] Travis for 18.11 stable branch Aaron Conole
2019-05-14 12:57 ` Kevin Traynor [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=4eba40b4-29e4-3c07-050e-46b410bc8010@redhat.com \
--to=ktraynor@redhat.com \
--cc=aconole@redhat.com \
--cc=msantana@redhat.com \
--cc=stable@dpdk.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).