From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [PATCH v3 0/2] custom doc styling
Date: Wed, 31 Jul 2024 17:38:23 +0100 [thread overview]
Message-ID: <7110c0a1-a9f2-49f5-a203-c7284af8b22f@amd.com> (raw)
In-Reply-To: <6502280.j6PcuT4dK6@thomas>
On 7/31/2024 5:22 PM, Thomas Monjalon wrote:
> 31/07/2024 17:57, Thomas Monjalon:
>> 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
>
> Applied with background color fixed.
>
You already applied, but let me give my explicit ack for record:
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
prev parent reply other threads:[~2024-07-31 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 9:15 [PATCH " Thomas Monjalon
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 [this message]
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=7110c0a1-a9f2-49f5-a203-c7284af8b22f@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).