From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Community CI Meeting Minutes - August 27, 2020
Date: Wed, 2 Sep 2020 17:28:54 -0400 [thread overview]
Message-ID: <CAOE1vsPfdBPYi2h0nJ1Qa81ppz-P-TzWdf+YbvC_yitT4LTMuw@mail.gmail.com> (raw)
In-Reply-To: <3121835.8k2kvKekyj@thomas>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Added https://bugs.dpdk.org/show_bug.cgi?id=534 to track this.
On Wed, Sep 2, 2020 at 5:25 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 02/09/2020 23:22, Lincoln Lavoie:
> > On Wed, Sep 2, 2020 at 4:43 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> > > 27/08/2020 20:49, Lincoln Lavoie:
> > > > Intel Lab
> > > > * Working on transition to Meson build, which will be needed for
> > > > the 2020.11 release (tracked BUG-xyz)
> > >
> > > We can stop testing "make" on the main branch.
> > > Meson will be the only supported build system starting 20.11 release.
> >
> > I thought we had said that would happen with the 20.11 release, but up
> > until then, we should keep running it.
>
> I would recommend stopping now for main branch.
> It doesn't make sense rejecting a patch which breaks "make",
> especially the patches removing "make" support ;)
>
>
>
--
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2347 bytes --]
prev parent reply other threads:[~2020-09-02 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 18:49 Lincoln Lavoie
2020-09-01 13:16 ` Ali Alnubani
2020-09-02 20:43 ` Thomas Monjalon
2020-09-02 21:22 ` Lincoln Lavoie
2020-09-02 21:25 ` Thomas Monjalon
2020-09-02 21:28 ` Lincoln Lavoie [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=CAOE1vsPfdBPYi2h0nJ1Qa81ppz-P-TzWdf+YbvC_yitT4LTMuw@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=ci@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).