All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] doc: show version in html guides
Date: Fri, 18 Dec 2015 12:41:24 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202409E30@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <69070363.GR6IPDgz4Q@xps13>


> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, December 18, 2015 10:46 AM
> To: Mcnamara, John
> Cc: dev@dpdk.org
> Subject: Re: [PATCH] doc: show version in html guides
> 
> 2015-12-18 10:27, Mcnamara, John:
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > The version does not appear in the readthedocs theme.
> > > We may try to customize the theme, or just update the project name
> > > as in this patch. The project name is not used in the PDF.
> >
> > Hi,
> >
> > I see the version number in generated docs:
> >
> >     http://i.imgur.com/GkvNz2U.png
> 
> Interesting.
> 
> > However, I can see that it doesn't appear on the dpdk.org version.
> >
> > I am using:
> >
> >     $ sphinx-build --version
> >     Sphinx (sphinx-build) 1.3.1
> 
> Same version on dpdk.org.
> There should be something else different...


It could be the version of the RTD theme:


    $ python -c "import sphinx_rtd_theme; print sphinx_rtd_theme.__version__"
    0.1.9

0.1.9 is required for the version number in the Navbar:

    https://github.com/snide/sphinx_rtd_theme#v0-1-9

John.
-- 

  reply	other threads:[~2015-12-18 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 10:26 [PATCH] doc: show version in html guides Thomas Monjalon
2015-12-18 10:27 ` Mcnamara, John
2015-12-18 10:46   ` Thomas Monjalon
2015-12-18 12:41     ` Mcnamara, John [this message]
2015-12-18 16: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=B27915DBBA3421428155699D51E4CFE202409E30@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.