From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Walter Harms <wharms@bfs.de>, Benjamin Peterson <benjamin@python.org>
Cc: mtk.manpages@gmail.com,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"jwilk@jwilk.net" <jwilk@jwilk.net>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: AW: [PATCH v2] exit.3: Use hex for the status mask.
Date: Mon, 24 Feb 2020 08:59:05 +0100 [thread overview]
Message-ID: <ccec6131-fa76-0b23-8ec1-83560f05e1a5@gmail.com> (raw)
In-Reply-To: <64833eb8e6064d3aba5583b88c36c022@bfs.de>
On 2/10/20 12:02 PM, Walter Harms wrote:
> Its a bit late but ...
>
> we can be more direct here:
>
>> +function causes normal process termination and the value of \fIstatus &
>> +0xFF\fP is returned to the parent (see
>
> function causes normal process termination and only lowest 8 bits
> (\fIstatus & 0xFF\fP) is returned to the parent (see
Thanks, Walter. I agree that it would not hurt to use a bit more
natural language in the description. I made the text:
The exit() function causes normal process termination and the
least significant byte of status (i.e., status & 0xFF) is returned
to the parent (see wait(2)).
Thanks for the suggestion.
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-02-24 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1537033056.1989189.1509225696.4324DB3A@webmail.messagingengine.com>
[not found] ` <20180915173848.19733-1-benjamin@python.org>
2020-02-08 11:00 ` [PATCH v2] exit.3: Use hex for the status mask Michael Kerrisk (man-pages)
2020-02-10 11:02 ` AW: " Walter Harms
2020-02-24 7:59 ` Michael Kerrisk (man-pages) [this message]
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=ccec6131-fa76-0b23-8ec1-83560f05e1a5@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=benjamin@python.org \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=vapier@gentoo.org \
--cc=wharms@bfs.de \
/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).