Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Swati Sharma <swati2.sharma@intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] Add support for prehistoric sphinx versions
Date: Wed, 29 Mar 2023 17:56:33 +0530	[thread overview]
Message-ID: <b2a499aa-f79b-ba66-b22a-adce4fd3dec4@intel.com> (raw)
In-Reply-To: <20230329111954.2584660-1-mauro.chehab@linux.intel.com>

LGTM

Reviewed-by: Swati Sharma <swati2.sharma@intel.com>

On 29-Mar-23 4:49 PM, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
> 
> Ubuntu 18.04 comes with a prehistoric version of Sphinx. While
> upstream is currently on version 6.1.x, Ubuntu comes with version
> 1.6.
> 
> Yet, adding support for it is not hard, as it is just a matter of
> adjusting the theme setup logic.
> 
> Mauro Carvalho Chehab (2):
>    conf.py: add some backward-compatibility bits
>    docs/testplan/conf.py: avoid using shutil include
> 
>   docs/testplan/conf.py | 46 +++++++++++++++++++++++++++++++++++--------
>   1 file changed, 38 insertions(+), 8 deletions(-)
> 

-- 
~Swati Sharma


  parent reply	other threads:[~2023-03-29 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 11:19 [igt-dev] [PATCH i-g-t 0/2] Add support for prehistoric sphinx versions Mauro Carvalho Chehab
2023-03-29 11:19 ` [igt-dev] [PATCH i-g-t 1/2] conf.py: add some backward-compatibility bits Mauro Carvalho Chehab
2023-03-29 11:19 ` [igt-dev] [PATCH i-g-t 2/2] docs/testplan/conf.py: avoid using shutil include Mauro Carvalho Chehab
2023-03-29 12:10 ` [igt-dev] ✓ Fi.CI.BAT: success for Add support for prehistoric sphinx versions Patchwork
2023-03-29 12:26 ` Swati Sharma [this message]
2023-03-30  1:34 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=b2a499aa-f79b-ba66-b22a-adce4fd3dec4@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mauro.chehab@linux.intel.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