From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: move rel_notes instructions as comments
Date: Tue, 17 May 2016 07:54:11 +0200 [thread overview]
Message-ID: <28716726.MjP2ZFYKIL@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20254C23E@IRSMSX103.ger.corp.intel.com>
> > We don't want to have this instructions in the generated docs, so use
> > comments. It's also less confusing for people adding entries in the
> > documentation.
> >
> > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
>
> Good idea.
>
> Reviewed-by: John McNamara <john.mcnamara@intel.com>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-05-17 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 13:27 Olivier Matz
2016-05-16 11:08 ` Mcnamara, John
2016-05-16 14:16 ` Thomas Monjalon
2016-05-17 5:54 ` 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=28716726.MjP2ZFYKIL@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=olivier.matz@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).