From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] version: 17.05-rc0
Date: Fri, 17 Feb 2017 11:15:00 +0000 [thread overview]
Message-ID: <f0d686cd-ced5-ac82-36a2-042f14e51e28@intel.com> (raw)
In-Reply-To: <20170217105939.GA130516@bricha3-MOBL3.ger.corp.intel.com>
On 2/17/2017 10:59 AM, Bruce Richardson wrote:
> On Fri, Feb 17, 2017 at 11:42:20AM +0100, Thomas Monjalon wrote:
>> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Hi Thomas,
What do you think about tagging -rc0 releases?
I find it useful for "git describe" output, but not sure if it bloats
ref list.
Thanks,
ferruh
next prev parent reply other threads:[~2017-02-17 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 10:42 Thomas Monjalon
2017-02-17 10:59 ` Bruce Richardson
2017-02-17 11:15 ` Ferruh Yigit [this message]
2017-02-17 11:20 ` Thomas Monjalon
2017-02-17 11:18 ` 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=f0d686cd-ced5-ac82-36a2-042f14e51e28@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).