austin-group-l  

Messages by Thread

• [1003.1(2013)/Issue7+TC1 0001953]: getdelim() behavior is ambiguous on empty file Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001952]: (n)gettext and NLSPATH Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001952]: (n)gettext and NLSPATH Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2004)/Issue 6 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2004)/Issue 6 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2004)/Issue 6 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2004)/Issue 6 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2004)/Issue 6 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2004)/Issue 6 0001955]: Behaviour is unclear when a parameter expands to another valid expansion Austin Group Issue Tracker via austin-group-l at The Open Group
• Fwd: Why is F_DUPFD_CLOFORK_CLOEXEC not needed? Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Why is F_DUPFD_CLOFORK_CLOEXEC not needed? Dhruv McElwaine via austin-group-l at The Open Group
  • Re: Why is F_DUPFD_CLOFORK_CLOEXEC not needed? Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Why is F_DUPFD_CLOFORK_CLOEXEC not needed? Geoff Clare via austin-group-l at The Open Group
  • Re: Why is F_DUPFD_CLOFORK_CLOEXEC not needed? Steffen Nurpmeso via austin-group-l at The Open Group
• Hurt by DDoS defender? Niu Danny via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001954]: please allow shells to unignore signals Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001951]: getopts example oversight Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001951]: getopts example oversight Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001951]: getopts example oversight Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 23rd October 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001950]: Create a detached thread with a function that returns void Austin Group Issue Tracker via austin-group-l at The Open Group
• Interpretation proposed: bug 1913 Andrew Josey via austin-group-l at The Open Group
  • Re: Interpretation proposed: bug 1913 Andrew Josey via austin-group-l at The Open Group
• Alternate `sigaction` notification method Dhruv McElwaine via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001944]: posix_devctl() uses int for command where some ioctl() implementations use larger type Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001948]: indexing / xref issues regarding realpath and basename Austin Group Issue Tracker via austin-group-l at The Open Group
• austingroupbugs under DDOS attack Mark Brown via austin-group-l at The Open Group
• Minutes of the 9th October 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001947]: Repeated "the" in memmem, posix_devctl, posix_memalign Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001947]: Repeated "the" in memmem, posix_devctl, posix_memalign Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001947]: Repeated "the" in memmem, posix_devctl, posix_memalign Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001949]: Restore the traditional realloc(3) specification Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 25th September 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001942]: Add common options to diff Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001942]: Add common options to diff Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001942]: Add common options to diff Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001942]: Add common options to diff Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001942]: Add common options to diff Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001946]: do locale definition file global keywords allow 1-n blanks after the keyword or does it have to be 1 space Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001946]: do locale definition file global keywords allow 1-n blanks after the keyword or does it have to be 1 space Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001946]: do locale definition file global keywords allow 1-n blanks after the keyword or does it have to be 1 space Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001946]: do locale definition file global keywords allow 1-n blanks after the keyword or does it have to be 1 space Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 11th August 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001943]: Usage of "multibyte" vs "multi-byte" in the standard text Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001943]: Usage of "multibyte" vs "multi-byte" in the standard text Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0001942]: Add common options to diff Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001941]: Add widely-implemented options to grep Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 28th August 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 28th August 2025 Teleconference G. Branden Robinson via austin-group-l at The Open Group
  • Re: Minutes of the 28th August 2025 Teleconference Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Minutes of the 28th August 2025 Teleconference Geoff Clare via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001939]: find: -perm: add / modifier Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001940]: ed should ignore (or handle) SIGPIPE Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001940]: ed should ignore (or handle) SIGPIPE Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 14th August 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Interpretations proposed: bug 1938/1851 Andrew Josey via austin-group-l at The Open Group
• Mantis: default Project; moving of an issue between projects Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Mantis: default Project; moving of an issue between projects Geoff Clare via austin-group-l at The Open Group
  • Re: Mantis: default Project; moving of an issue between projects Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Mantis: default Project; moving of an issue between projects Steffen Nurpmeso via austin-group-l at The Open Group
• Call reminder August 14 2025 Andrew Josey via austin-group-l at The Open Group
• Implementing POSIX-2024 ERE. Niu Danny via austin-group-l at The Open Group
• [Issue 8 drafts 0001933]: make: example 7 contains text for two separate topics Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 24th July 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001938]: scandir() should set errno to indicate the error Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001938]: scandir() should set errno to indicate the error Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001938]: scandir() should set errno to indicate the error Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001936]: timer_create synopsis uses clockid while rest of it's specification uses clock_id Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001936]: timer_create synopsis uses clockid while rest of it's specification uses clock_id Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001935]: posix_spawn file actions: in the context of the child or "as if" in the context of the child? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001935]: posix_spawn file actions: in the context of the child or "as if" in the context of the child? Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001934]: ex's suspend command and job control Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001934]: ex's suspend command and job control Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001934]: ex's suspend command and job control Austin Group Issue Tracker via austin-group-l at The Open Group
• Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • 回复: Long command line arguments Niu Danny via austin-group-l at The Open Group
  • Re: Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • Re: Long command line arguments Niu Danny via austin-group-l at The Open Group
  • Re: Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • Re: Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • Re: Long command line arguments Niu Danny via austin-group-l at The Open Group
  • Re: Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • Re: Long command line arguments Niu Danny via austin-group-l at The Open Group
  • Re: Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • Re: Long command line arguments Guy Harris via austin-group-l at The Open Group
  • Re: Long command line arguments Hans Åberg via austin-group-l at The Open Group
  • Re: Long command line arguments Guy Harris via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001937]: Undefined behavior in tsearch EXAMPLES text Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001937]: Undefined behavior in tsearch EXAMPLES text Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001937]: Undefined behavior in tsearch EXAMPLES text Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001937]: Undefined behavior in tsearch EXAMPLES text Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 17th July 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001931]: Behavior of scandir() when no entries are selected Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001931]: Behavior of scandir() when no entries are selected Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001931]: Behavior of scandir() when no entries are selected Geoff Clare via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001931]: Behavior of scandir() when no entries are selected Austin Group Issue Tracker via austin-group-l at The Open Group
• Pseudo-code for cross checking implementations. Niu Danny via austin-group-l at The Open Group
• Minutes of the 10th July 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Is Boost mis-interpreting the left-most longest semantic? Niu Danny via austin-group-l at The Open Group
  • Re: Is Boost mis-interpreting the left-most longest semantic? Niu Danny via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001929]: features of SOCK_SEQPACKET in documentation of certain System Interfaces contradict its definition in the Base Definitions Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001929]: features of SOCK_SEQPACKET in documentation of certain System Interfaces contradict its definition in the Base Definitions Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 26th June 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Unsubscribe Roger Barraud via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001932]: termios: should cfsetospeed(B0) trigger SIGHUP? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001932]: termios: should cfsetospeed(B0) trigger SIGHUP? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001932]: termios: should cfsetospeed(B0) trigger SIGHUP? Austin Group Issue Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001931]: Behavior of scandir() when no entries are selected Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 19th June 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• A short critique of online pub page for pax. Niu Danny via austin-group-l at The Open Group
  • Re: A short critique of online pub page for pax. Geoff Clare via austin-group-l at The Open Group
  • Re: A short critique of online pub page for pax. Niu Danny via austin-group-l at The Open Group
  • Re: A short critique of online pub page for pax. Geoff Clare via austin-group-l at The Open Group
  • Re: A short critique of online pub page for pax. Niu Danny via austin-group-l at The Open Group
• Minutes of the 12th June 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• XSH RFC: pthread_gettid for obtaining an integral thread identifier Trevor Gross via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001928]: `void *` shown as `void` in <search.h> page Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001928]: `void *` shown as `void` in <search.h> page Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001928]: `void *` shown as `void` in <search.h> page Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001928]: `void *` shown as `void` in <search.h> page Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001928]: `void *` shown as `void` in <search.h> page Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0001011]: Make the binary search tree functions friendlier to use: require balancing, add typing and allow destruction Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2008)/Issue 7 0001927]: Add sponge utility Steffen Nurpmeso via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2008)/Issue 7 0001927]: Add sponge utility Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: [1003.1(2008)/Issue 7 0001927]: Add sponge utility Steffen Nurpmeso via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001927]: Add sponge utility Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 5th June 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001926]: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001926]: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001926]: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001926]: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001926]: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001926]: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? Austin Group Issue Tracker via austin-group-l at The Open Group
• Opinion over alternative localization mechanisms among standard developers (was: Re: About regex, charset, and localization.) Niu Danny via austin-group-l at The Open Group
  • Re: Opinion over alternative localization mechanisms among standard developers (was: Re: About regex, charset, and localization.) Niu Danny via austin-group-l at The Open Group
• About regex, charset, and localization. Niu Danny via austin-group-l at The Open Group
  • Re: About regex, charset, and localization. EuAndreh via austin-group-l at The Open Group
  • Re: About regex, charset, and localization. Niu Danny via austin-group-l at The Open Group
  • Re: About regex, charset, and localization. Niu Danny via austin-group-l at The Open Group
  • Re: About regex, charset, and localization. [email protected] via austin-group-l at The Open Group
  • Re: About regex, charset, and localization. Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: About regex, charset, and localization. Niu Danny via austin-group-l at The Open Group
• Minutes of the 15th May 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Interpretation proposed: bug 1925 Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group

• Earlier messages
• Later messages