From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Mat Martineau
<mathew.j.martineau-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Stephan Mueller
<smueller-T9tCv8IpfcWELgA04lAiVw@public.gmane.org>,
keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 1/6] keyctl.2: change "is" to "was" in error descriptions
Date: Sat, 2 Sep 2017 06:40:03 +0200 [thread overview]
Message-ID: <20170902044003.GA7303@asgard.redhat.com> (raw)
Since half of items used "was" and another half used "is".
---
man2/keyctl.2 | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 63109f9..3469947 100644
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -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
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-09-02 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 4:40 Eugene Syromyatnikov [this message]
[not found] ` <20170902044003.GA7303-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2017-09-03 0:14 ` [PATCH v2 1/6] keyctl.2: change "is" to "was" in error descriptions Michael Kerrisk (man-pages)
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=20170902044003.GA7303@asgard.redhat.com \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mathew.j.martineau-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smueller-T9tCv8IpfcWELgA04lAiVw@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox