From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216876] New: prototype for execveat() in the documentation appears wrong
Date: Mon, 02 Jan 2023 03:47:47 +0000 [thread overview]
Message-ID: <bug-216876-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216876
Bug ID: 216876
Summary: prototype for execveat() in the documentation appears
wrong
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: low
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: markgaleck@gmail.com
Regression: No
prototype for execveat() in the documentation is:
int execveat(int dirfd, const char *pathname,
const char *const argv[], const char *const envp[],
int flags);
This appears to be inconsistent with similar functions, other documentation,
and my sources (latest Ubuntu distribution).
I think two of the "const" should be dropped so that we should have:
int execveat(int dirfd, const char *pathname,
char *const argv[], char *const envp[],
int flags);
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-01-02 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 3:47 bugzilla-daemon [this message]
2023-01-02 15:26 ` [Bug 216876] prototype for execveat() in the documentation appears wrong bugzilla-daemon
2023-05-19 13:21 ` bugzilla-daemon
2023-05-19 13:23 ` bugzilla-daemon
[not found] <bug-216876-216477@https.bugzilla.kernel.org/>
2023-01-02 15:02 ` [Bug 216876] New: " Alejandro Colomar
2023-01-02 15:26 ` Florian Weimer
2023-01-02 16:12 ` Alejandro Colomar
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=bug-216876-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.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).