From: Frank Rowand <frowand.list@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Tim.Bird@sony.com, Brendan Higgins <brendanhiggins@google.com>,
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 10:06:35 -0500 [thread overview]
Message-ID: <ceab750d-c107-9273-3718-9632085362b3@gmail.com> (raw)
In-Reply-To: <Yw4InUF5TpR/wdwb@casper.infradead.org>
On 8/30/22 07:54, Matthew Wilcox wrote:
> On Mon, Aug 29, 2022 at 06:31:49PM -0500, 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
>> ===================================================
>
> Hey Frank, you can actually use overlength lines to prevent this kind of
> problem from occurring. eg, this is perfectly acceptable:
>
> ===================================================================
> Hi
> ===================================================================
>
> I wonder if we should prefer this style to avoid the rash of complaints
> when a headline is changed.
Thanks, that is useful to know. I think it might be a good idea to
switch to the longer style at some point before the final version 2
release.
-Frank
next prev parent reply other threads:[~2022-08-30 15:06 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
2022-08-30 15:04 ` Frank Rowand
2022-08-30 12:54 ` Matthew Wilcox
2022-08-30 15:06 ` Frank Rowand [this message]
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=ceab750d-c107-9273-3718-9632085362b3@gmail.com \
--to=frowand.list@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.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 \
--cc=willy@infradead.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