From: Bagas Sanjaya <bagasdotme@gmail.com>
To: frowand.list@gmail.com, David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Tim.Bird@sony.com, Brendan Higgins <brendanhiggins@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
rmr167@gmail.com, guillaume.tucker@collabora.com,
dlatypov@google.com, kernelci@groups.io,
kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] ktap_v2: change version to 2-rc in KTAP specification
Date: Tue, 30 Aug 2022 08:48:32 +0700 [thread overview]
Message-ID: <eaf6c56b-c329-2d02-7599-ca83dbe20b0b@gmail.com> (raw)
In-Reply-To: <20220829233150.3564612-2-frowand.list@gmail.com>
On 8/30/22 06:31, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Prepare KTAP Specification for the process of creating version 2.
>
> The version will remain "2-rc" until the final commit to complete
> Version 2. Adding the "-rc" ensures that none of the development
> versions will be mistaken for the completed version 2.
>
> After this commit, Sphinx complains that we now need more '=' signs:
>
> Documentation/dev-tools/ktap.rst:3: WARNING: Title overline too short.
> ===================================================
> The Kernel Test Anything Protocol (KTAP), version 2-rc
> ===================================================
>
> This warning will disappear in the final commit for the release of
> version 2, when the "-rc" is removed.
>
I don't see that -rc stripping in patch [2/2], so please fix the Sphinx
warning above in this patch.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-08-30 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:31 [PATCH v3 0/2] begin KTAP spec v2 process frowand.list
2022-08-29 23:31 ` [PATCH v3 1/2] ktap_v2: change version to 2-rc in KTAP specification frowand.list
2022-08-30 1:48 ` Bagas Sanjaya [this message]
2022-08-30 15:04 ` Frank Rowand
2022-08-30 12:54 ` Matthew Wilcox
2022-08-30 15:06 ` Frank Rowand
2022-08-29 23:31 ` [PATCH v3 2/2] ktap_v2: change "version 1" to "version 2" in examples frowand.list
2022-08-30 22:16 ` [PATCH v3 0/2] begin KTAP spec v2 process Frank Rowand
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=eaf6c56b-c329-2d02-7599-ca83dbe20b0b@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=frowand.list@gmail.com \
--cc=guillaume.tucker@collabora.com \
--cc=keescook@chromium.org \
--cc=kernelci@groups.io \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmr167@gmail.com \
--cc=skhan@linuxfoundation.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