From: Richard Haines <richard_c_haines@btinternet.com>
To: selinux@vger.kernel.org
Cc: paul@paul-moore.com, Richard Haines <richard_c_haines@btinternet.com>
Subject: [PATCH Notebook] Reference Policy: Module versioning now optional
Date: Mon, 4 Apr 2022 09:37:46 +0100 [thread overview]
Message-ID: <20220404083746.5929-1-richard_c_haines@btinternet.com> (raw)
Since Reference Policy release 2.20220106 the version_number argument
is optional. If missing '1' is set as a default to satisfy the policy
syntax.
Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
---
src/modular_policy_statements.md | 4 +++-
src/reference_policy.md | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/modular_policy_statements.md b/src/modular_policy_statements.md
index e62e6ac..c0caa62 100644
--- a/src/modular_policy_statements.md
+++ b/src/modular_policy_statements.md
@@ -35,7 +35,9 @@ The *module* name.
*version_number*
The module version number in M.m.m format (where M = major version number
-and m = minor version numbers).
+and m = minor version numbers). Since Reference Policy release 2.20220106
+the *version_number* argument is optional. If missing '1' is set as a default
+to satisfy the policy syntax.
**The statement is valid in:**
diff --git a/src/reference_policy.md b/src/reference_policy.md
index ebb516f..f96949a 100644
--- a/src/reference_policy.md
+++ b/src/reference_policy.md
@@ -1820,7 +1820,9 @@ policy_module(module_name,version)
*version_number*
- The module version number in M.m.m format (where M = major version number
- and m = minor version numbers).
+ and m = minor version numbers). Since release 2.20220106 the *version_number*
+ argument is optional. If missing '1' is set as a default to satisfy the
+ policy syntax.
**The macro is valid in:**
--
2.35.1
next reply other threads:[~2022-04-04 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 8:37 Richard Haines [this message]
2022-04-04 21:34 ` [PATCH Notebook] Reference Policy: Module versioning now optional Paul Moore
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=20220404083746.5929-1-richard_c_haines@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.