keyctl.2: change "is" to "was" in error descriptions
PATCH v2 1/6 keyctl.2: change "is" to "was" in error descriptions
Since half of items used "was" and another half used "is".
--- man2/keyctl.2 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
man2/keyctl.2 +6 -6
@@ -1537,7 +1537,7 @@ The requested operation wasn't permitted. .TP .B EDEADLK .I operation -is +was .BR KEYCTL_LINK and the requested link would result in a cycle. .TP
@@ -1585,14 +1585,14 @@ A revoked key was found or specified. .TP .B ELOOP .I operation -is +was .BR KEYCTL_LINK and the requested link would cause the maximum nesting depth for keyrings to be exceeded. .TP .BR ENFILE " (Linux kernels before 3.13)" .IR operation -is +was .BR KEYCTL_LINK and the keyring is full. (Before Linux 3.13,
@@ -1602,7 +1602,7 @@ a single page of memory; since Linux 3.13, there is no fixed limit.) .TP .B ENOENT .I operation -is +was .B KEYCTL_UNLINK and the key to be unlinked isn't linked to the keyring. .TP
@@ -1626,7 +1626,7 @@ a different type was provided. .TP .B EOPNOTSUPP .I operation -is +was .B KEYCTL_READ and the key type does not support reading (e.g., the type is
@@ -1634,7 +1634,7 @@ and the key type does not support reading .TP .B EOPNOTSUPP .I operation -is +was .B KEYCTL_UPDATE and the key type does not support updating. .TP
Signature · 1 line
2.1.4
A message that is not in the archive (sent off-list or not yet received): 20170902044003.GA7303-ZbobWygYI+YXGNroddHbYwC/[email protected]
Hi Eugene,
Quoted 1 line · Eugene Syromyatnikov
Since half of items used "was" and another half used "is".
Yes, that makes sense. Applied
Cheers,
Michael
Quoted 62 lines
--- man2/keyctl.2 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)man2/keyctl.2 +6
-6@@ -1537,7 +1537,7 @@ The requested operation wasn't permitted. .TP .B EDEADLK .I operation -is +was .BR KEYCTL_LINK and the requested link would result in a cycle. .TP@@ -1585,14 +1585,14 @@ A revoked key was found or specified. .TP .B ELOOP .I operation -is +was .BR KEYCTL_LINK and the requested link would cause the maximum nesting depth for keyrings to be exceeded. .TP .BR ENFILE " (Linux kernels before 3.13)" .IR operation -is +was .BR KEYCTL_LINK and the keyring is full. (Before Linux 3.13,@@ -1602,7 +1602,7 @@ a single page of memory; since Linux 3.13, there is no fixed limit.) .TP .B ENOENT .I operation -is +was .B KEYCTL_UNLINK and the key to be unlinked isn't linked to the keyring. .TP@@ -1626,7 +1626,7 @@ a different type was provided. .TP .B EOPNOTSUPP .I operation -is +was .B KEYCTL_READ and the key type does not support reading (e.g., the type is@@ -1634,7 +1634,7 @@ and the key type does not support reading .TP .B EOPNOTSUPP .I operation -is +was .B KEYCTL_UPDATE and the key type does not support updating. .TP
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/