DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Butler, Siobhan A" <siobhan.a.butler@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] split programmers guide a bit
Date: Tue, 31 Mar 2015 11:34:02 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2F001CD@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2548676.I0KaJlYG5K@xps13>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, March 31, 2015 12:38 AM
> To: Butler, Siobhan A
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 0/3] split programmers guide a bit
> 
> 2015-03-19 17:48, Thomas Monjalon:
> > Too many things are included in the programmers guide.
> > I think it should cover only API and knowledge needed to make an
> application.
> > That's why I suggest to move Xen and NICs doc outside.
> > Then it will be easier to add doc for a new environment or a new NIC.
> > Note that drivers or device-related libs like KNI, vhost or bonding
> > stay in the programmer's guide because they are more high-level than
> NICs drivers.
> >
> > Changes in v2:
> > - create index for Xen guide
> > - rename figure links
> > - rebase with mlx4
> > - HTML copyright removal has been sent separately
> >
> > Thomas Monjalon (3):
> >   doc: fix file attributes
> >   doc: move Xen guide out of programmers guide
> >   doc: nics guide
> 
> Applied with figures list restored on Bernard's request.

Hi,

Any objection to an additional patch to move the figure captions below the figures in the docs?

The caption above the figure was the format used in the initial docs, and it looks okay in the HTML output, but in the PDF output it tends to get merged into the preceding paragraph and isn't always on the same page as the figure.

John

  reply	other threads:[~2015-03-31 11:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 23:35 [dpdk-dev] [RFC PATCH 0/4] welcome doc for new nics and environments Thomas Monjalon
2015-01-31 23:35 ` [dpdk-dev] [RFC PATCH 1/4] doc: fix file attributes Thomas Monjalon
2015-01-31 23:35 ` [dpdk-dev] [RFC PATCH 2/4] doc: move Xen guide out of programmers guide Thomas Monjalon
2015-01-31 23:35 ` [dpdk-dev] [RFC PATCH 3/4] doc: nics guide Thomas Monjalon
2015-01-31 23:35 ` [dpdk-dev] [RFC PATCH 4/4] doc: remove copyright footer Thomas Monjalon
     [not found] ` <1678582.gq5SofjDC3@xps13>
     [not found]   ` <8CEF83825BEC744B83065625E567D7C2049DCD83@IRSMSX108.ger.corp.intel.com>
     [not found]     ` <1500004.RM7mZx5SlJ@xps13>
2015-02-02 17:54       ` [dpdk-dev] [RFC PATCH 3/4] doc: nics guide Iremonger, Bernard
2015-03-19 16:48 ` [dpdk-dev] [PATCH v2 0/3] split programmers guide a bit Thomas Monjalon
2015-03-19 16:48   ` [dpdk-dev] [PATCH v2 1/3] doc: fix file attributes Thomas Monjalon
2015-03-19 18:03     ` Butler, Siobhan A
2015-03-19 16:48   ` [dpdk-dev] [PATCH v2 2/3] doc: move Xen guide out of programmers guide Thomas Monjalon
2015-03-19 18:03     ` Butler, Siobhan A
2015-03-19 16:48   ` [dpdk-dev] [PATCH v2 3/3] doc: nics guide Thomas Monjalon
2015-03-19 17:36     ` Iremonger, Bernard
2015-03-19 18:02     ` Butler, Siobhan A
2015-03-30 23:38   ` [dpdk-dev] [PATCH v2 0/3] split programmers guide a bit Thomas Monjalon
2015-03-31 11:34     ` Mcnamara, John [this message]
2015-03-31 12:23       ` Thomas Monjalon
2015-04-01  9:19         ` Iremonger, Bernard
2015-04-01 16:36           ` Mcnamara, John
2015-04-01 17:20             ` Iremonger, Bernard
2015-04-02  7:59               ` Mcnamara, John
2015-04-02 11:04       ` [dpdk-dev] [RFC] doc: refactored figure numbers into references John McNamara

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=B27915DBBA3421428155699D51E4CFE2F001CD@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=siobhan.a.butler@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).