From: "Andrew G. Morgan" <morgan@kernel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: LSM List <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH 16/16] capsh.c: Spelling fixes in usage() message
Date: Thu, 16 Jul 2020 08:08:20 -0700 [thread overview]
Message-ID: <CALQRfL6dAEgiUiEckUN9x_g0J+sywz+Q_zBfPqPFTBsf2zRt=A@mail.gmail.com> (raw)
In-Reply-To: <20200716101827.162793-16-mtk.manpages@gmail.com>
Thanks! Applied all of them except 07_16. Instead, I've hopefully
clarified the intent of the text with some quotes.
Cheers
Andrew
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=34e4e00b983a2c0fc5f13b403871a8fb5860bb89
On Thu, Jul 16, 2020 at 3:19 AM Michael Kerrisk (man-pages)
<mtk.manpages@gmail.com> wrote:
>
> Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
> ---
> progs/capsh.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/progs/capsh.c b/progs/capsh.c
> index 94bf57d..7bed98e 100644
> --- a/progs/capsh.c
> +++ b/progs/capsh.c
> @@ -879,10 +879,10 @@ int main(int argc, char *argv[], char *envp[])
> " --delamb=xxx remove xxx,... capabilities from ambient\n"
> " --noamb reset (drop) all ambient capabilities\n"
> " --caps=xxx set caps as per cap_from_text()\n"
> - " --inh=xxx set xxx,.. inheritiable set\n"
> + " --inh=xxx set xxx,.. inheritable set\n"
> " --secbits=<n> write a new value for securebits\n"
> " --iab=... use cap_iab_from_text() to set iab\n"
> - " --keep=<n> set keep-capabability bit to <n>\n"
> + " --keep=<n> set keep-capability bit to <n>\n"
> " --uid=<n> set uid to <n> (hint: id <username>)\n"
> " --cap-uid=<n> libcap cap_setuid() to change uid\n"
> " --is-uid=<n> exit 1 if uid != <n>\n"
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-07-16 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 10:18 [PATCH 01/16] Manual pages: getcap.8, getpcaps.8, setcap.8: SEE ALSO: add capabilities(7) Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 02/16] Manual pages: cap_get_file.3, getcap.8, setcap.8: SEE ALSO: add user_namespaces(7) Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 03/16] Manual pages: setcap.8: Formatting fix: use bold for function name Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 04/16] Manual pages: cap_from_text.3: typo fix Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 05/16] Manual pages: cap_get_file.3, getcap.8, setcap.8: clarify "namespace" Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 06/16] Manual pages: cap_get_file.3: Remove stray macros that have no effect Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 07/16] Manual pages: cap_get_proc.3: s/UNCERTAIN/CAP_MODE_UNCERTAIN/ Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 08/16] Manual pages: cap_get_proc.3: formatting fix Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 09/16] Manual pages: capsh.1: spelling fixes Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 10/16] Manual pages: capsh.1: Remove stray .TP macro Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 11/16] Manual pages: capsh.1: Correct/update the Cap field example for /proc/PID/status Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 12/16] Manual pages: capsh.1: Update the capsh --decode example Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 13/16] Manual pages: capsh.1: Describe the argument of --secbits in more detail Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 14/16] pam_cap.c: Spelling fix in output string Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 15/16] Various source files: spelling fixes on comments Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 16/16] capsh.c: Spelling fixes in usage() message Michael Kerrisk (man-pages)
2020-07-16 15:08 ` Andrew G. Morgan [this message]
2020-07-17 6:00 ` 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='CALQRfL6dAEgiUiEckUN9x_g0J+sywz+Q_zBfPqPFTBsf2zRt=A@mail.gmail.com' \
--to=morgan@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mtk.manpages@gmail.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 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.