From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Lance Richardson <lance.richardson@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] 19.08 scheduling question
Date: Wed, 29 May 2019 16:39:13 +0100 [thread overview]
Message-ID: <1c5982c0-71f7-2f43-5718-6500599abbdc@intel.com> (raw)
In-Reply-To: <CADyeNED0JHCdQDjLNwxM=j6chj60r1VVyjKo3JQ2sp2y8esUjA@mail.gmail.com>
On 5/29/2019 4:29 PM, Lance Richardson wrote:
> This page gives a "proposal deadline" of June 3 for the 19.08 release:
>
> https://core.dpdk.org/roadmap/
>
> Apologies if this is a faq, but is the "proposal" simply a v1 patch
> set implementing the proposed change, or is some other mechanism to be
> used?
It is simply v1 patch.
prev parent reply other threads:[~2019-05-29 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 15:29 Lance Richardson
2019-05-29 15:39 ` Ferruh Yigit [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=1c5982c0-71f7-2f43-5718-6500599abbdc@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=lance.richardson@broadcom.com \
/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).