From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, Aaron Conole <aconole@redhat.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] Reorganise Travis jobs
Date: Thu, 20 Feb 2020 22:05:19 +0100 [thread overview]
Message-ID: <CAJFAV8zPmTJ130M7hxkyQcnWYNc4C3Zni76C-6mKJ_s8uCjM4A@mail.gmail.com> (raw)
In-Reply-To: <20200219194131.29417-1-david.marchand@redhat.com>
On Wed, Feb 19, 2020 at 8:41 PM David Marchand
<david.marchand@redhat.com> wrote:
> This series tries to make the travis configuration a bit easier to read,
> then drops jobs that are not essential or functional duplicates in the
> hope we can give some oxygen to the robot who seems to lag quite a bit
> and can't catch up.
Travis cache for master flushed.
Series applied.
--
David Marchand
prev parent reply other threads:[~2020-02-20 21:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:41 David Marchand
2020-02-19 19:41 ` [dpdk-dev] [PATCH 1/4] ci: remove unnecessary dependency on Linux headers David Marchand
2020-02-20 10:44 ` Thomas Monjalon
2020-02-20 14:37 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 2/4] ci: fix Travis config warnings David Marchand
2020-02-20 11:03 ` Thomas Monjalon
2020-02-20 12:09 ` David Marchand
2020-02-20 16:46 ` David Marchand
2020-02-20 21:01 ` Aaron Conole
2020-02-21 10:17 ` Thomas Monjalon
2020-02-20 14:36 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 3/4] ci: use an explicit list of Travis jobs David Marchand
2020-02-20 11:05 ` Thomas Monjalon
2020-02-20 14:35 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 4/4] ci: reorganise " David Marchand
2020-02-19 21:39 ` Aaron Conole
2020-02-20 10:42 ` Thomas Monjalon
2020-02-20 12:22 ` David Marchand
2020-02-20 14:35 ` Aaron Conole
2020-02-20 16:01 ` David Marchand
2020-02-20 19:38 ` [dpdk-dev] [dpdk-ci] " Jeremy Plsek
2020-02-20 0:18 ` [dpdk-dev] " dwilder
2020-02-20 11:07 ` Thomas Monjalon
2020-02-20 21:05 ` David Marchand [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=CAJFAV8zPmTJ130M7hxkyQcnWYNc4C3Zni76C-6mKJ_s8uCjM4A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).