From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: remove wrong document description
Date: Tue, 29 Nov 2016 10:58:45 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20266AC83@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20161129105421.lzcgiuygbbjabaur@tarshish>
> -----Original Message-----
> From: Baruch Siach [mailto:baruch@tkos.co.il]
> Sent: Tuesday, November 29, 2016 10:54 AM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH] doc: remove wrong document description
>
> Hi John,
>
> On Tue, Nov 29, 2016 at 09:54:58AM +0000, Mcnamara, John wrote:
> > > -----Original Message-----
> > > From: Baruch Siach [mailto:baruch@tkos.co.il]
> > > Sent: Tuesday, November 29, 2016 9:26 AM
> > > To: dev@dpdk.org
> > > Cc: Mcnamara, John <john.mcnamara@intel.com>; Baruch Siach
> > > <baruch@tkos.co.il>
> > > Subject: [PATCH] doc: remove wrong document description
> > >
> > > The Programmer’s Guide intro is not the Release Notes.
> > >
> > > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> >
> > Thanks for the fix.
> >
> > I would be in favour of removing the entire "Documentation Roadmap"
> > and "Related Publications" sections. I meant to do that in the past.
> >
> > As for this patch:
> >
> > Acked-by: John McNamara <john.mcnamara@intel.com>
>
> Thanks. For some reason patchwork didn't get your ack.
Strange. I worked for one I acked shortly afterwards.
I'll try once more.
John
next prev parent reply other threads:[~2016-11-29 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 9:25 Baruch Siach
2016-11-29 9:54 ` Mcnamara, John
2016-11-29 10:54 ` Baruch Siach
2016-11-29 10:58 ` Mcnamara, John [this message]
2016-11-29 20:38 ` Thomas Monjalon
2016-11-29 10:59 ` Mcnamara, John
2016-12-06 17:03 ` 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=B27915DBBA3421428155699D51E4CFE20266AC83@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=baruch@tkos.co.il \
--cc=dev@dpdk.org \
/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).