kernelci.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Rae Moar <rmoar@google.com>
To: frowand.list@gmail.com, davidgow@google.com,
	keescook@chromium.org,  Tim.Bird@sony.com, shuah@kernel.org,
	brendanhiggins@google.com
Cc: tytso@google.com, gustavo.padovan@collabora.com,
	 ricardo.canuelo@collabora.com, corbet@lwn.net,
	kernelci@lists.linux.dev,  linux-kselftest@vger.kernel.org,
	kunit-dev@googlegroups.com,  linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	 Frank Rowand <frank.rowand@sony.com>,
	Rae Moar <rmoar@google.com>
Subject: [PATCH 1/5] ktap_v2: change version to 2-rc in KTAP specification
Date: Tue, 12 Nov 2024 20:07:44 +0000	[thread overview]
Message-ID: <20241112200748.791828-2-rmoar@google.com> (raw)
In-Reply-To: <20241112200748.791828-1-rmoar@google.com>

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.

Reviewed-by: Rae Moar <rmoar@google.com>
Signed-off-by: Frank Rowand <frank.rowand@sony.com>
Signed-off-by: Rae Moar <rmoar@google.com>
---
 Documentation/dev-tools/ktap.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/dev-tools/ktap.rst b/Documentation/dev-tools/ktap.rst
index 414c105b10a9..333193f51a53 100644
--- a/Documentation/dev-tools/ktap.rst
+++ b/Documentation/dev-tools/ktap.rst
@@ -1,7 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0
 
 ===================================================
-The Kernel Test Anything Protocol (KTAP), version 1
+The Kernel Test Anything Protocol (KTAP), version 2-rc
 ===================================================
 
 TAP, or the Test Anything Protocol is a format for specifying test results used
-- 
2.47.0.277.g8800431eea-goog


  reply	other threads:[~2024-11-12 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 20:07 [PATCH 0/5] release of KTAP version 2 Rae Moar
2024-11-12 20:07 ` Rae Moar [this message]
2024-11-12 20:07 ` [PATCH 2/5] ktap_v2: change "version 1" to "version 2" in examples Rae Moar
2024-11-12 20:07 ` [PATCH 3/5] ktap_v2: add test metadata Rae Moar
2024-11-12 20:07 ` [PATCH 4/5] ktap_v2: formatting fixes to ktap spec Rae Moar
2024-11-12 20:07 ` [PATCH 5/5] ktap_v2: change version to 2 in KTAP specification Rae Moar

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=20241112200748.791828-2-rmoar@google.com \
    --to=rmoar@google.com \
    --cc=Tim.Bird@sony.com \
    --cc=brendanhiggins@google.com \
    --cc=corbet@lwn.net \
    --cc=davidgow@google.com \
    --cc=frank.rowand@sony.com \
    --cc=frowand.list@gmail.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=keescook@chromium.org \
    --cc=kernelci@lists.linux.dev \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=ricardo.canuelo@collabora.com \
    --cc=shuah@kernel.org \
    --cc=tytso@google.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;
as well as URLs for NNTP newsgroup(s).