From: Vincent JARDIN <vincent.jardin@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] releases scheduling
Date: Tue, 15 Dec 2015 22:40:45 +0100 [thread overview]
Message-ID: <567088DD.1070203@6wind.com> (raw)
In-Reply-To: <7C846718-93F5-46D4-BD1F-6D618C192973@intel.com>
On 15/12/2015 22:15, Wiles, Keith wrote:
> I see the YY.MM.PP (PP is patch number) as the simplest way to keep track of when a release was done.
+1
I like it.
next prev parent reply other threads:[~2015-12-15 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 19:22 Thomas Monjalon
2015-12-15 13:37 ` O'Driscoll, Tim
2015-12-15 14:24 ` Arnon Warshavsky
2015-12-15 14:42 ` Wiles, Keith
2015-12-15 15:39 ` Jay Rolette
2015-12-15 19:15 ` Dave Neary
2015-12-15 21:15 ` Wiles, Keith
2015-12-15 21:40 ` Vincent JARDIN [this message]
2015-12-19 0:01 ` Thomas Monjalon
2015-12-19 2:16 ` Wiles, Keith
2015-12-19 9:47 ` Thomas Monjalon
2015-12-19 16:21 ` Wiles, Keith
2015-12-19 20:13 ` Thomas Monjalon
2015-12-19 22:58 ` O'Driscoll, Tim
2015-12-27 20:04 ` Thomas Monjalon
2016-05-12 9:38 Thomas Monjalon
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=567088DD.1070203@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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).