From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: Ethernet API - multiple post-RX-burst callbacks' run-order is opposite to their add-order
Date: Fri, 10 Jul 2015 16:02:13 +0200 [thread overview]
Message-ID: <4695548.DNsLn0eCMG@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F6A411@IRSMSX103.ger.corp.intel.com>
2015-07-10 13:52, Mcnamara, John:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > If the patch is accepted I'll add a note to the release notes also.
> >
> > Why not doing the release notes change atomicly in the same patch?
>
> Mainly, because there isn't currently a clear place to do that in the
> release notes. I could change the "New Features" section to "New Features
> in 2.0" and then add a "New Features in 2.1". Or perhaps this needs to go
> into a "Changed Features in 2.1" section. If you have a suggestion I'll
> follow it.
I think we should reset "new features" at the beginning of the release cycle.
Maybe that the "supported features" section needs a refresh also.
> And I support your previous suggestion of updating the release notes
> in patchsets. That would make things easier for the release notes
> maintainers (me and you mainly).
You mean asking to every developers to update the release notes?
Just to be sure we are on the same line.
> Perhaps I'll kick off a separate thread of discussion on refactoring
> the release notes to make them more useful and easier to update.
OK thanks
prev parent reply other threads:[~2015-07-10 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 21:04 Ethernet API - multiple post-RX-burst callbacks' run-order is opposite to their add-order Sanford, Robert
2015-07-03 9:57 ` Bruce Richardson
2015-07-03 10:02 ` Thomas Monjalon
2015-07-10 13:14 ` Mcnamara, John
2015-07-10 13:24 ` Thomas Monjalon
2015-07-10 13:52 ` Mcnamara, John
2015-07-10 14:02 ` Thomas Monjalon [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=4695548.DNsLn0eCMG@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.