public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/22099] getconf help info
Date: Sat, 13 Apr 2024 18:35:46 +0000 [thread overview]
Message-ID: <bug-22099-131-PuJD9ze1Lx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22099-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22099
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Eric Blake from comment #2)
> The Austin Group pointed out one of the ambiguities of the GNU output when
> encountering multi-line confstr() output:
>
> $ getconf POSIX_V7_WIDTH_RESTRICTED_ENVS
> POSIX_V7_ILP32_OFF32
> POSIX_V7_ILP32_OFFBIG
> POSIX_V7_LP64_OFF64
> $ getconf -a | grep -A2 V7_WIDTH
> _POSIX_V7_WIDTH_RESTRICTED_ENVS POSIX_V7_ILP32_OFF32
> POSIX_V7_ILP32_OFFBIG
> POSIX_V7_LP64_OFF64
> POSIX_V7_WIDTH_RESTRICTED_ENVS POSIX_V7_ILP32_OFF32
> POSIX_V7_ILP32_OFFBIG
> POSIX_V7_LP64_OFF64
>
> and recommends that GNU consider changing the output to be more like BSD
> output, using a colon between the item name and its value (as it is less
> likely for a confstr() output to also contain a colon)
Colon between name and value, or colon between multiple values (instead of
newlines)?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-13 18:35 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 [this message]
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
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-PuJD9ze1Lx@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).