From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "'dev@dpdk.org'" <dev@dpdk.org>
Subject: [dpdk-dev] Question about images in the docs
Date: Tue, 31 Mar 2015 13:35:48 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2F0037F@IRSMSX103.ger.corp.intel.com> (raw)
Hi Bernard,
If you get a break during your training could you drop up to me or I can drop down to you.
I have a quick question about how the images are template in the docs.
John
> -----Original Message-----
> From: Mcnamara, John
> Sent: Tuesday, March 31, 2015 12:34 PM
> To: Thomas Monjalon; Butler, Siobhan A; Iremonger, Bernard
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2 0/3] split programmers guide a bit
>
> > -----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 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=B27915DBBA3421428155699D51E4CFE2F0037F@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.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).