[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41fe0989-9157-944d-c796-21e28c8265b9@gmail.com>
Date: Sat, 1 Oct 2022 10:07:47 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: David Gow <davidgow@...gle.com>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
KUnit Development <kunit-dev@...glegroups.com>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Brendan Higgins <brendan.higgins@...ux.dev>,
Jonathan Corbet <corbet@....net>,
Khalid Masum <khalid.masum.92@...il.com>,
Sadiya Kazi <sadiyakazi@...gle.com>
Subject: Re: [PATCH v2] Documentation: kunit: rewrite writing first test
instructions
On 9/30/22 17:32, David Gow wrote:
>>
>> The indentation for code-block directive is required, since the preceding
>> paragraph is multiline; otherwise there will be Sphinx warnings.
>>
>
> I don't see any such warnings on my machine (which claims to have
> sphinx-build 4.5.0).
>
> Could you send an example warning, and your sphinx version to me so I
> can try to reproduce it.
>
> Regardless, if it's causing warnings, keep these changes. (Though it'd
> be nice to include the warnings in the commit message, so it's obvious
> that these are being re-aligned for a reason.)
>
I'm using Sphinx 2.4.4 (as installed from pip through
Documentation/sphinx/requirements.txt).
Sorry I can't reproduce the warning I mentioned earlier (I forget
the recipe that triggers it when writing the improv).
In any case, I'd like to keep code block aligning in the separate patch.
It would be nice to see code blocks aligned to the instructions list.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists