[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cca4e4ae-0a37-83ea-c740-1085b59a3e1c@gmail.com>
Date: Wed, 4 May 2022 18:04:49 -0500
From: Frank Rowand <frowand.list@...il.com>
To: David Gow <davidgow@...gle.com>,
Shuah Khan <skhan@...uxfoundation.org>,
Kees Cook <keescook@...omium.org>, Tim.Bird@...y.com,
Brendan Higgins <brendanhiggins@...gle.com>
Cc: Jonathan Corbet <corbet@....net>, rmr167@...il.com,
guillaume.tucker@...labora.com, dlatypov@...gle.com,
kernelci@...ups.io, kunit-dev@...glegroups.com,
linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] begin KTAP spec v2 process
On 5/4/22 17:51, frowand.list@...il.com wrote:
> From: Frank Rowand <frank.rowand@...y.com>
>
> The process to create version 2 of the KTAP Specification is documented
> in email discussions. I am attempting to capture this information at
>
> https://elinux.org/Test_Results_Format_Notes#KTAP_version_2
>
> I am already not following the suggested process, which says:
> "...please try to follow this principal of one major topic per email
> thread." I think that is ok in this case because the two patches
> are related and (hopefully) not controversial.
>
> Changes since patch version 1:
> - drop patch 1/2. Jonathan Corbet has already applied this patch
> into version 1 of the Specification
> - rename patch 2/2 to patch 1/2, with updated patch comment
> - add new patch 2/2
>
> Frank Rowand (2):
> ktap_v2: change version to 2-rc in KTAP specification
> ktap_v2: change "version 1" to "version 2" in examples
>
> Documentation/dev-tools/ktap.rst | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
I should note that I will be maintaining a branch of the KTAP Specification version 2
patches and that they will not be submitted to mainline until we agree on the final
content of version 2.
Powered by blists - more mailing lists