From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PULL REQUEST] doc: document modifications in user guides
Date: Wed, 03 Dec 2014 19:44:39 +0100 [thread overview]
Message-ID: <8976301.UG4oOl51AQ@xps13> (raw)
In-Reply-To: <1417621813-24826-1-git-send-email-bernard.iremonger@intel.com>
Hi Bernard,
These patches won't pulled as is for 2 reasons:
1) I made some comments recently on some of these patches
2) It appears you didn't applied the v5 of Pablo's patchset
http://dpdk.org/ml/archives/dev/2014-December/009270.html
Below some title rewording to make it concise and more consistent:
2014-12-03 15:50, Bernard Iremonger:
> Bruce Richardson (3):
> doc: change hardcoded date to auto-generated in guide documents
doc: auto-generate date in guides
> doc: adjust line lengths in freebsd getting started guide rst files
doc: adjust line lengths in freebsd guide
> doc: update freebsd getting started guide to document ports install
doc: add freebsd ports
>
> Doherty, Declan (1):
> doc: link bonding related updates to programmers guide
doc: update bonding
>
> Pablo de Lara (4):
> doc: added new commands in testpmd application user guide
doc: new testpmd commands
> doc: fix commands in testpmd application user guide
doc: fix testpmd commands
> doc: moved commands in testpmd application user guide to match testpmd command help order
doc: reorder testpmd commands
> doc: fixes in testpmd application user guide
doc: fix testpmd guide
>
> Siobhan Butler (4):
> doc: added distributor sample application to the sample application user guide
doc: add distributor application
> doc: add vhost library section in programmers guide
doc: add vhost library
> doc: updated i40e enabling additonal functionality in linux getting started guide
doc: update i40e
> doc: remove references to intel dpdk in linux getting started guide
--
Thomas
next prev parent reply other threads:[~2014-12-03 18:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <REQUEST PULL>
2014-10-23 14:35 ` [dpdk-dev] [PULL REQUEST] doc: freebsd getting started guide Bernard Iremonger
2014-10-29 22:26 ` Thomas Monjalon
2014-10-31 16:25 ` [dpdk-dev] [PULL REQUEST] doc: release notes, programmers guide, sample app. guide and fix to linux " Bernard Iremonger
2014-10-31 18:07 ` Thomas Monjalon
2014-11-03 18:02 ` Thomas Monjalon
2014-11-17 9:41 ` [dpdk-dev] [PULL REQUEST] doc: programmers guide Bernard Iremonger
2014-11-18 14:01 ` Thomas Monjalon
2014-11-20 15:36 ` [dpdk-dev] [PULL REQUEST] doc: Various document fixes in testpmd UG Bernard Iremonger
2014-11-26 11:37 ` [dpdk-dev] [PULL REQUEST] doc: document modifications in testpmd_app_ug and freebsd_gsg Bernard Iremonger
2014-12-03 15:50 ` [dpdk-dev] [PULL REQUEST] doc: document modifications in user guides Bernard Iremonger
2014-12-03 18:44 ` Thomas Monjalon [this message]
2014-12-04 11:22 ` Iremonger, Bernard
2014-12-04 15:34 ` [dpdk-dev] [PULL REQUEST] doc: modifications to " Bernard Iremonger
2014-12-05 16:23 ` Thomas Monjalon
2014-12-11 14:13 ` Bernard Iremonger
2014-12-17 0:15 ` Thomas Monjalon
2014-12-18 21:29 ` Bernard Iremonger
2014-12-19 17:40 ` [dpdk-dev] [PULL REQUEST] doc: latest " Bernard Iremonger
2014-12-19 22:47 ` 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=8976301.UG4oOl51AQ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bernard.iremonger@intel.com \
--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).