On 08/26/2016 03:36 PM, Darren Hart wrote:
The revision rules limit revision names to C-language numerical
representations, but incorrectly include "1.3.1" and similar.
Update the section to only include valid C-language numerical strings.
Signed-off-by: Darren Hart <dvhart(a)infradead.org>
---
documentation/database_rules.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/database_rules.txt b/documentation/database_rules.txt
index 2ab7b0a..924a70b 100644
--- a/documentation/database_rules.txt
+++ b/documentation/database_rules.txt
@@ -74,10 +74,10 @@ name represents the largest value, when compared.
Revision names may consist of groupings of ASCII digits separated by a
'.', or any numeric value commonly used in the C language. Comparison
is from left to right, and values are compared numerically; any group
-not present is assumed to be zero. For example, '1.4' > '1.3.1',
+not present is assumed to be zero. For example, '1.4' > '1.3',
'0x01040000' > '0x01030100', and '20160421' >
'20160312'. New revisions
must always be greater than any existing revisions; i.e., you cannot add
-revision '1.3.1' if '1.4' already exists.
+revision '131' if '140' already exists.
The rules regarding the creation of new revisions of a property set are
set in the section on immutability that follows. At least one revision
Applied. Thanks!
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------