DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [PATCH 0/2] custom doc styling
Date: Sun, 21 Jul 2024 11:15:20 +0200	[thread overview]
Message-ID: <20240721095351.355639-1-thomas@monjalon.net> (raw)

The file custom.css allows to change the theme from "Read the Docs".
The first patch makes it available without "ninja install".
The second patch allows the NIC overview tables to be "fullscreen".

Thomas Monjalon (2):
  doc: copy custom CSS on guides build
  doc: give full width to NIC overview page

 buildtools/call-sphinx-build.py | 9 +++++++++
 doc/guides/custom.css           | 8 ++++++++
 doc/guides/meson.build          | 2 --
 doc/guides/nics/overview.rst    | 2 ++
 4 files changed, 19 insertions(+), 2 deletions(-)

-- 
2.45.0


             reply	other threads:[~2024-07-21  9:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21  9:15 Thomas Monjalon [this message]
2024-07-21  9:15 ` [PATCH 1/2] doc: copy custom CSS on guides build Thomas Monjalon
2024-07-21  9:15 ` [PATCH 2/2] doc: give full width to NIC overview page Thomas Monjalon
2024-07-31  8:31 ` [PATCH v2 0/2] custom doc styling Thomas Monjalon
2024-07-31  8:31   ` [PATCH v2 1/2] doc: copy custom CSS on guides build Thomas Monjalon
2024-07-31 11:25     ` Ferruh Yigit
2024-07-31  8:31   ` [PATCH v2 2/2] doc: give full width to NIC overview page Thomas Monjalon
2024-07-31 11:29     ` Ferruh Yigit
2024-07-31 12:43       ` Thomas Monjalon
2024-07-31 15:56         ` Thomas Monjalon
2024-07-31 15:57 ` [PATCH v3 0/2] custom doc styling Thomas Monjalon
2024-07-31 15:57   ` [PATCH v3 1/2] doc: copy custom CSS on guides build Thomas Monjalon
2024-07-31 15:57   ` [PATCH v3 2/2] doc: give full width to NIC overview page Thomas Monjalon
2024-07-31 16:17     ` Ferruh Yigit
2024-07-31 16:21       ` Thomas Monjalon
2024-07-31 16:22   ` [PATCH v3 0/2] custom doc styling Thomas Monjalon
2024-07-31 16:38     ` Ferruh Yigit

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=20240721095351.355639-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --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).