From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, David Marchand <david.marchand@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] version: 19.08-rc0
Date: Tue, 14 May 2019 22:34:37 -0700 [thread overview]
Message-ID: <20190514223437.3835641b@hermes.lan> (raw)
Message-ID: <20190515053437.fsrRtWFZgQDYmgzC-97D3UjvuflJgoHkqMPUc7jt4ho@z> (raw)
In-Reply-To: <1635899.lKKcTi1DVh@xps>
On Tue, 14 May 2019 23:00:17 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 14/05/2019 18:32, David Marchand:
> > On Tue, May 14, 2019 at 6:08 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > > Start a new release cycle with empty release notes.
> > >
> > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > Reviewed-by: David Marchand <david.marchand@redhat.com>
>
> Applied
>
> 19.08 release cycle is now officially started!
> Please don't forget to fill the release notes in the patches
> adding some outstanding features.
>
What are the plans for all the patches you marked deferred in the closing
days of 19.05? Will you review them?
next prev parent reply other threads:[~2019-05-15 5:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 16:07 Thomas Monjalon
2019-05-14 16:07 ` Thomas Monjalon
2019-05-14 16:32 ` David Marchand
2019-05-14 16:32 ` David Marchand
2019-05-14 21:00 ` Thomas Monjalon
2019-05-14 21:00 ` Thomas Monjalon
2019-05-15 5:34 ` Stephen Hemminger [this message]
2019-05-15 5:34 ` Stephen Hemminger
2019-05-15 7:29 ` Thomas Monjalon
2019-05-15 7:29 ` Thomas Monjalon
2019-05-15 7:29 ` David Marchand
2019-05-15 7:29 ` David Marchand
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=20190514223437.3835641b@hermes.lan \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).