public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eblake at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/22099] getconf help info Date: Wed, 17 Apr 2024 19:25:36 +0000 [thread overview] Message-ID: <bug-22099-131-i9DmH61b4r@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-22099-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=22099 --- Comment #7 from Eric Blake <eblake at redhat dot com> --- The POSIX wording is not set in stone; if we have a better proposal (possibly under the guise of a different option) than the current difference in output between BSD getopt and glibc getopt, right now is our chance to propose that to the Austin Group. BSD does have 'getopt -l' which lists the known names (but not values) that can be queried; the Austin Group did discuss that as being one possibility, but at the time said that it has fewer implementations than 'getopt -a'. But if we can argue back to the Austin Group that 'getopt -l' is the better interface from the get-go, and implement it such that the output is equivalent to BSD's output, then it stands a better chance of the Austin Group standardizing 'getopt -l' and leaving 'getopt -a' as an unspecified extension option. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-17 19:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-22099-131@http.sourceware.org/bugzilla/> 2024-04-08 15:30 ` eblake at redhat dot com 2024-04-11 15:14 ` eblake at redhat dot com 2024-04-13 18:35 ` fweimer at redhat dot com 2024-04-15 12:34 ` eblake at redhat dot com 2024-04-15 12:46 ` eblake at redhat dot com 2024-04-17 17:11 ` fweimer at redhat dot com 2024-04-17 19:25 ` eblake at redhat dot com [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=bug-22099-131-i9DmH61b4r@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).