From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "David Harton (dharton)" <dharton@cisco.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Tahhan, Maryam" <maryam.tahhan@intel.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"Horton, Remy" <remy.horton@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce xstats api change for 16.07
Date: Wed, 6 Apr 2016 13:53:26 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6128A4421@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <9edf0e7ca1854e7cbb013359cb6423a8@XCH-RCD-016.cisco.com>
> From: David Harton (dharton) [mailto:dharton@cisco.com]
> Subject: RE: [dpdk-dev] [PATCH] doc: announce xstats api change for 16.07
> > This should not be the normal process.
> > It is important to understand what should be the changes to decide of
> > announcing or not a deprecation.
> > In the case of the mempool reworks, the patch have been sent and discussed
> > on the mailing list.
> > Given the previous explanations (and knowing you did good job on stats), I
> > give my
> > Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> Thanks for considering this.
Would you mind giving the patch an Ack David?
Then we'll have the 3 Acks needed and can fix this in the next release.
Cheers, -Harry
next prev parent reply other threads:[~2016-04-06 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 17:58 Harry van Haaren
2016-04-05 18:45 ` Thomas Monjalon
2016-04-06 9:02 ` Van Haaren, Harry
2016-04-06 9:22 ` Thomas Monjalon
2016-04-06 11:16 ` Van Haaren, Harry
2016-04-06 12:14 ` Thomas Monjalon
2016-04-06 13:49 ` David Harton (dharton)
2016-04-06 13:53 ` Van Haaren, Harry [this message]
2016-04-06 13:46 ` Remy Horton
2016-04-06 14:00 ` David Harton (dharton)
2016-04-06 14:25 ` Tahhan, Maryam
2016-04-07 21:36 ` 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=E923DB57A917B54B9182A2E928D00FA6128A4421@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=dharton@cisco.com \
--cc=maryam.tahhan@intel.com \
--cc=olivier.matz@6wind.com \
--cc=remy.horton@intel.com \
--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).