austin-group-l  

Messages by Thread

• • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001647]: printf("%lc", (wint_t)0) can't output NUL byte Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001643]: fprintf %lc: wrong reference to the current conversion specification Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001643]: fprintf %lc: wrong reference to the current conversion specification Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001643]: fprintf %lc: wrong reference to the current conversion specification Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001642]: DUMB terminal is not defined Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001642]: DUMB terminal is not defined Austin Group Bug Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2016/18)/Issue7+TC2 0001642]: DUMB terminal is not defined Steffen Nurpmeso via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001642]: DUMB terminal is not defined Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001630]: Alias names Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001630]: Alias names Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001630]: Alias names Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001254]: "asynchronous list" description uses "command" instead of "AND-OR list" Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001675]: Copy and paste error in new job control section Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001675]: Copy and paste error in new job control section Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001675]: Copy and paste error in new job control section Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001675]: Copy and paste error in new job control section Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0001044]: Calling setsid as part of posix_spawn Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001044]: Calling setsid as part of posix_spawn Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker via austin-group-l at The Open Group
• XCU nl -l described in terms of "blank lines", all implementations actually use empty lines; -l works across sections наб via austin-group-l at The Open Group
• XCU nl carries vestigial LC_CTYPE which contradicts other text since Issue 5 наб via austin-group-l at The Open Group
• XCU nl STDOUT bears no relation to actual output from real implementations (unnumbered lines) наб via austin-group-l at The Open Group
  • XCU nl STDOUT bears no relation to actual output from real implementations (unnumbered lines) наб via austin-group-l at The Open Group
  • Re: XCU nl STDOUT bears no relation to actual output from real implementations (heading lines) наб via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001674]: may posix_spawnp() fail with ENOEXEC? Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001673]: Rationale about removed interfaces needs updating Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001673]: Rationale about removed interfaces needs updating Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001673]: Rationale about removed interfaces needs updating Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001672]: Wording improvement to lockf() APPLICATION USAGE Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001672]: Wording improvement to lockf() APPLICATION USAGE Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001672]: Wording improvement to lockf() APPLICATION USAGE Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001672]: Wording improvement to lockf() APPLICATION USAGE Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0000768]: add "fd-private" POSIX locks to spec Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0000768]: add "fd-private" POSIX locks to spec Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001671]: OFD-owned locks addition missed some changes Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001671]: OFD-owned locks addition missed some changes Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001671]: OFD-owned locks addition missed some changes Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001671]: OFD-owned locks addition missed some changes Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001274]: pid_t must fit in an int for definition of fcntl to be consistent. Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001670]: F_GETOWN_EX and F_SETOWN_EX missing from fcntl() RETURN VALUE Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001670]: F_GETOWN_EX and F_SETOWN_EX missing from fcntl() RETURN VALUE Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001670]: F_GETOWN_EX and F_SETOWN_EX missing from fcntl() RETURN VALUE Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001670]: F_GETOWN_EX and F_SETOWN_EX missing from fcntl() RETURN VALUE Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001418]: Add options to ulimit to match get/setrlimit() Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000051]: sh exit status not clear for built-in terminated by a signal Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001669]: Make the ulimit utility consistent with [gs]etrlimit() wrt XSI Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001669]: Make the ulimit utility consistent with [gs]etrlimit() wrt XSI Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001669]: Make the ulimit utility consistent with [gs]etrlimit() wrt XSI Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001669]: Make the ulimit utility consistent with [gs]etrlimit() wrt XSI Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001669]: Make the ulimit utility consistent with [gs]etrlimit() wrt XSI Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 13th April 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Restarting: Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Restarting: Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
• [Issue 8 drafts 0001668]: Math-related functions are conceptually async-cancel-safe. Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001668]: Math-related functions are conceptually async-cancel-safe. Austin Group Bug Tracker via austin-group-l at The Open Group
• Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
  • Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001667]: [gs]etres[gu]id() should be async-signal-safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001667]: [gs]etres[gu]id() should be async-signal-safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001667]: [gs]etres[gu]id() should be async-signal-safe Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001667]: [gs]etres[gu]id() should be async-signal-safe Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001344]: Addition of setresuid()/setresgid()/getresuid()/getresgid() Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001666]: getresgid() and getresuid() are missing "restrict" Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001666]: getresgid() and getresuid() are missing "restrict" Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001666]: getresgid() and getresuid() are missing "restrict" Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001666]: getresgid() and getresuid() are missing "restrict" Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001666]: getresgid() and getresuid() are missing "restrict" Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000658]: Undefined/unspecified behavior clauses in description of open have race conditions Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001665]: Contradictory text in descriptions of O_EXEC and O_SEARCH Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001665]: Contradictory text in descriptions of O_EXEC and O_SEARCH Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001665]: Contradictory text in descriptions of O_EXEC and O_SEARCH Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001665]: Contradictory text in descriptions of O_EXEC and O_SEARCH Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001665]: Contradictory text in descriptions of O_EXEC and O_SEARCH Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0000696]: either NAME_MAX shouldn't be optional, or readdir_r() needs clarification Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001664]: Some readdir() non-normative text needs updating to reflect normative text changes Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001664]: Some readdir() non-normative text needs updating to reflect normative text changes Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001664]: Some readdir() non-normative text needs updating to reflect normative text changes Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001664]: Some readdir() non-normative text needs updating to reflect normative text changes Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001663]: Remove XSI shading from realpath() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001663]: Remove XSI shading from realpath() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001663]: Remove XSI shading from realpath() Austin Group Bug Tracker via austin-group-l at The Open Group
• Re: $? behaviour after comsub in same command Chet Ramey via austin-group-l at The Open Group
• [Issue 8 drafts 0001551]: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters) Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001662]: Delimiter issues in ed and ex Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001662]: Delimiter issues in ed and ex Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001662]: Delimiter issues in ed and ex Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001662]: Delimiter issues in ed and ex Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed Austin Group Bug Tracker via austin-group-l at The Open Group

• Later messages