austin-group-l  

Messages by Thread

• Interpretation proposed: 0001966: Current/previous job definition scattered and ambiguous Andrew Josey via austin-group-l at The Open Group
• Any interest in MSG_TRUNC? Niu Danny via austin-group-l at The Open Group
• Minutes of the 2nd April 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 26th March 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 12th March 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001974]: tabs: wrong description of semantics of arbitrary tab stops Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001973]: awk "numeric string " origins Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 5th March 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001973]: awk "string variables" origin Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001973]: awk "string variables" origin Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001973]: awk "string variables" origin Stephane Chazelas via austin-group-l at The Open Group
• "interpretation proposed" status Stephane Chazelas via austin-group-l at The Open Group
  • Re: "interpretation proposed" status Andrew Josey via austin-group-l at The Open Group
  • Re: "interpretation proposed" status Stephane Chazelas via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001971]: Changing lex prefixes Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001971]: Changing lex prefixes Austin Group Issue Tracker via austin-group-l at The Open Group
• Interpretation Proposed: Bug 0001970: exit status unclear for iconv -c on invalid input Andrew Josey via austin-group-l at The Open Group
• Interpretation Proposed: Bug 0001969: strptime() %y with a 1 digit field Andrew Josey via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001970]: exit status unclear for iconv -c on invalid input Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 26th February 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• This weeks meeting cancelled, next scheduled for 26th Feb Andrew Josey via austin-group-l at The Open Group
• Minutes of the 5th February 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 5th February 2026 Teleconference Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Minutes of the 5th February 2026 Teleconference Stephane Chazelas via austin-group-l at The Open Group
  • Re: Minutes of the 5th February 2026 Teleconference Mats Wichmann via austin-group-l at The Open Group
  • Re: Minutes of the 5th February 2026 Teleconference Geoff Clare via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001966]: Current/previous job definition scattered and ambiguous Austin Group Issue Tracker via austin-group-l at The Open Group
• Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Jonathan Wakely via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? David A. Wheeler via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? David A. Wheeler via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Niu Danny via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? G. Branden Robinson via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Andries E. Brouwer via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Jonathan Wakely via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Guy Harris via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Oğuz via austin-group-l at The Open Group
  • Re: Will the Open Group consider incorporating software security features in its software technical standards given the fact that these days lots of software are getting hacked? Amit via austin-group-l at The Open Group
• Minutes of the 22nd January 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• Interpretation Proposed: 0001965: Why isn't pthread_equal async-signal safe? Andrew Josey via austin-group-l at The Open Group
• Minutes of the 15th January 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001965]: Why isn't pthread_equal async-signal safe? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001965]: Why isn't pthread_equal async-signal safe? Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001965]: Why isn't pthread_equal async-signal safe? Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 8th January 2026 Teleconference Andrew Josey via austin-group-l at The Open Group
• Call reminder and POSIX Status report January 2026 Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001963]: sccs create should use get Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001963]: sccs create should use get Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001963]: sccs create should use get Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001963]: sccs create should use get Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001963]: sccs create should use get Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001959]: dd conv=lcase and conv=ucase should only translate single byte locales Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001962]: Remove FORTRAN support from the file utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001962]: Remove FORTRAN support from the file utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001962]: Remove FORTRAN support from the file utility Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 11th December 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Interpretation Proposed: 0001959: dd conv=lcase and conv=ucase should only translate single byte locales Andrew Josey via austin-group-l at The Open Group
  • Interpretation Proposed: 0001959: dd conv=lcase and conv=ucase should only translate single byte locales Andrew Josey via austin-group-l at The Open Group
  • Interpretations Proposed: 1961/1963 Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Steffen Nurpmeso via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001960]: fcntl(): add F_DUPFD_CLOFORKEXEC flag Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001957]: Standardize the -u option for ex/vi Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 4th December 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001956]: Standardise event queue based asynchronous io. Austin Group Issue Tracker via austin-group-l at The Open Group
• Austin Group WEBEX +1-408-792-6300 PIN 2553 332 6777 (Updated call information) Single UNIX Specification via austin-group-l at The Open Group
• austingroupbugs.net 403 Forbidden on any access Brian Inglis via austin-group-l at The Open Group
  • Re: austingroupbugs.net 403 Forbidden on any access Mark Brown via austin-group-l at The Open Group
  • Re: austingroupbugs.net 403 Forbidden on any access [email protected] via austin-group-l at The Open Group
  • Re: austingroupbugs.net 403 Forbidden on any access Guy Harris via austin-group-l at The Open Group
• Minutes of the 13th November 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 13th November 2025 Teleconference G. Branden Robinson via austin-group-l at The Open Group
• [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
• 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

• Earlier messages