linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 4/4] Changes.old: tfix
Date: Wed, 02 Dec 2015 17:13:18 +0100	[thread overview]
Message-ID: <565F189E.2070500@gmail.com> (raw)
In-Reply-To: <1445525054-2880-4-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

Thanks, Jakub. Applied.

Cheers,

Michael


On 10/22/2015 04:44 PM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
> ---
>  Changes.old | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Changes.old b/Changes.old
> index 28761a2..16429ab 100644
> --- a/Changes.old
> +++ b/Changes.old
> @@ -24576,7 +24576,7 @@ epoll_wait.2
>                  (LONG_MAX - 999ULL) / HZ)
>  
>              That is, the limit depends on the size of a long and the timer
> -            frequency.  Assuming the a long is never smaller than 32 bits
> +            frequency.  Assuming the long is never smaller than 32 bits
>              and HZ never larger than 1000, the worst case is 35 minutes.
>              I think this should be mentioned under "BUGS".
>  
> @@ -29396,7 +29396,7 @@ recv.2
>          Rework and reorganize the text in various parts of the page.
>          Isolate details specific to recv() vs recvfrom() vs recvmsg()
>              Place details specific to each system call under a
> -            a separate subheading.
> +            separate subheading.
>          Rework discussion of 'src_addr' and 'addrlen' for recvfrom()
>          Add description of 'buf' and 'len' in recvfrom() section
>          'addrlen' should be 0 (*not* NULL) when 'src_addr' is NULL
> @@ -38173,7 +38173,7 @@ stat.2
>              Recent changes to various pages employ this distinction.
>      Michael Kerrisk
>          Tighten wording: use 'mode bit' rather than 'permission bit'
> -            According to POSIX, the the 9 UGO*RWX bits are permissions, and
> +            According to POSIX, the 9 UGO*RWX bits are permissions, and
>              'mode' is used to refer to collectively to those bits plus sticky,
>              set-UID, and set_GID bits.
>  
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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

  parent reply	other threads:[~2015-12-02 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 14:44 [PATCH 1/4] bpf.2: tfix Jakub Wilk
     [not found] ` <1445525054-2880-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-10-22 14:44   ` [PATCH 2/4] tee.2: tfix Jakub Wilk
     [not found]     ` <1445525054-2880-2-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-10-23 11:38       ` Jakub Wilk
     [not found]         ` <20151023113853.GA4958-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-12-02 16:12           ` Michael Kerrisk (man-pages)
2015-10-22 14:44   ` [PATCH 3/4] " Jakub Wilk
     [not found]     ` <1445525054-2880-3-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-12-02 16:12       ` Michael Kerrisk (man-pages)
2015-10-22 14:44   ` [PATCH 4/4] Changes.old: tfix Jakub Wilk
     [not found]     ` <1445525054-2880-4-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-12-02 16:13       ` Michael Kerrisk (man-pages) [this message]
2015-12-02 16:11   ` [PATCH 1/4] bpf.2: tfix 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=565F189E.2070500@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).