austin-group-l
Thread
Date
Earlier messages
Later messages
Messages by Thread
[Issue 8 drafts 0001709]: Specify handling of '#' in macro definitions
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001708]: Use consistent wording for special targets
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001708]: Use consistent wording for special targets
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001708]: Use consistent wording for special targets
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001708]: Use consistent wording for special targets
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001708]: Use consistent wording for special targets
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001707]: Clarify meaning of 'use'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001707]: Clarify meaning of 'use'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001707]: Clarify meaning of 'use'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001707]: Clarify meaning of 'use'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001706]: Remove 'line that does not begin with <tab>' from the syntax for a rule
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001706]: Remove 'line that does not begin with <tab>' from the syntax for a rule
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001706]: Remove 'line that does not begin with <tab>' from the syntax for a rule
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001706]: Remove 'line that does not begin with <tab>' from the syntax for a rule
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001706]: Remove 'line that does not begin with <tab>' from the syntax for a rule
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001705]: Use 'to [the] standard output' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001705]: Use 'to [the] standard output' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001705]: Use 'to [the] standard output' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001704]: Use simpler wording for '+' prefix character
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001704]: Use simpler wording for '+' prefix character
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001704]: Use simpler wording for '+' prefix character
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001703]: Replace at-sign with <commercial-at>
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001703]: Replace at-sign with <commercial-at>
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001703]: Replace at-sign with <commercial-at>
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001703]: Replace at-sign with <commercial-at>
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001702]: Consistently use 'following' or 'next'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001702]: Consistently use 'following' or 'next'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001702]: Consistently use 'following' or 'next'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001702]: Consistently use 'following' or 'next'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001701]: Fix spelling of 'Inference Rules'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001701]: Fix spelling of 'Inference Rules'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001701]: Fix spelling of 'Inference Rules'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001700]: Clean up 'Makefile Syntax' section
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001700]: Clean up 'Makefile Syntax' section
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001700]: Clean up 'Makefile Syntax' section
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001699]: Use term 'rules' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001699]: Use term 'rules' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001699]: Use term 'rules' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001699]: Use term 'rules' consistently
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001698]: Replace 'a target' with 'the target'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001698]: Replace 'a target' with 'the target'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001698]: Replace 'a target' with 'the target'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001697]: Consider replacing out-of-date with not up-to-date
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001697]: Consider replacing out-of-date with not up-to-date
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001697]: Consider replacing out-of-date with not up-to-date
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001697]: Consider replacing out-of-date with not up-to-date
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001696]: Effect of -s when no work needs to be done
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001696]: Effect of -s when no work needs to be done
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001696]: Effect of -s when no work needs to be done
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001696]: Effect of -s when no work needs to be done
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001694]: Use consistent wording for 'in the order specified'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001694]: Use consistent wording for 'in the order specified'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001694]: Use consistent wording for 'in the order specified'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001693]: Align behavior of -s with existing practice
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001693]: Align behavior of -s with existing practice
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001693]: Align behavior of -s with existing practice
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001693]: Align behavior of -s with existing practice
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001693]: Align behavior of -s with existing practice
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001692]: Options -n, -q, -t use different wording
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001692]: Options -n, -q, -t use different wording
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001692]: Options -n, -q, -t use different wording
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001692]: Options -n, -q, -t use different wording
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001691]: Contradition for -n and ${MAKE}
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001691]: Contradition for -n and ${MAKE}
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001691]: Contradition for -n and ${MAKE}
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001691]: Contradition for -n and ${MAKE}
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001691]: Contradition for -n and ${MAKE}
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001690]: Use consistent wording for make's options
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001690]: Use consistent wording for make's options
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001690]: Use consistent wording for make's options
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001690]: Use consistent wording for make's options
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001689]: Maybe remove 'the user shall'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001689]: Maybe remove 'the user shall'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001689]: Maybe remove 'the user shall'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001688]: Scope is missing the "Additional APIs" documents and ISO TR24731-2
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001688]: Scope is missing the "Additional APIs" documents and ISO TR24731-2
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001688]: Scope is missing the "Additional APIs" documents and ISO TR24731-2
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001532]: "stty -g" output should not have to be split
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001687]: Mismatch between blanks in file formats and default IFS
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001687]: Mismatch between blanks in file formats and default IFS
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001687]: Mismatch between blanks in file formats and default IFS
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001687]: Mismatch between blanks in file formats and default IFS
Austin Group Bug Tracker via austin-group-l at The Open Group
automated linter UB checks for makefiles
Andrew Pennebaker via austin-group-l at The Open Group
Re: automated linter UB checks for makefiles
Oğuz İsmail Uysal via austin-group-l at The Open Group
Re: automated linter UB checks for makefiles
Andrew Pennebaker via austin-group-l at The Open Group
Minutes of the 27th April 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
[Issue 8 drafts 0001686]: Missing CX shading for underflow ERANGE in strtod() and wcstod()
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001686]: Missing CX shading for underflow ERANGE in strtod() and wcstod()
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001686]: Missing CX shading for underflow ERANGE in strtod() and wcstod()
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001685]: RFC references need updating
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001685]: RFC references need updating
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001685]: RFC references need updating
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001684]: Various fixed needed to subprofiling groups
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001684]: Various fixed needed to subprofiling groups
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001684]: Various fixed needed to subprofiling groups
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001684]: Various fixed needed to subprofiling groups
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001683]: nbyte cannot be negative in posix_devctl
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001683]: nbyte cannot be negative in posix_devctl
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001683]: nbyte cannot be negative in posix_devctl
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001682]: <libintl.h> should define locale_t
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001682]: <libintl.h> should define locale_t
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001682]: <libintl.h> should define locale_t
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001681]: <devctl.h> should define size_t
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001681]: <devctl.h> should define size_t
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001681]: <devctl.h> should define size_t
Austin Group Bug Tracker via austin-group-l at The Open Group
Minutes of the 20th April 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
[Issue 8 drafts 0001680]: Synopsis for make is missing '-j maxjobs'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001680]: Synopsis for make is missing '-j maxjobs'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001680]: Synopsis for make is missing '-j maxjobs'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001680]: Synopsis for make is missing '-j maxjobs'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001680]: Synopsis for make is missing '-j maxjobs'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001680]: Synopsis for make is missing '-j maxjobs'
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001679]: strictly increasing order vs. monotonic
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001679]: strictly increasing order vs. monotonic
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001679]: strictly increasing order vs. monotonic
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001679]: strictly increasing order vs. monotonic
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001678]: use correct word: "descendant"
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001678]: use correct word: "descendant"
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001678]: use correct word: "descendant"
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001678]: use correct word: "descendant"
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001678]: use correct word: "descendant"
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001677]: "Future Directions" text outdated
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001677]: "Future Directions" text outdated
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001677]: "Future Directions" text outdated
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001677]: "Future Directions" text outdated
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001677]: "Future Directions" text outdated
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001676]: spurious use of boldface
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001676]: spurious use of boldface
Austin Group Bug Tracker via austin-group-l at The Open Group
Re: [Issue 8 drafts 0001676]: spurious use of boldface
G. Branden Robinson via austin-group-l at The Open Group
[Issue 8 drafts 0001676]: spurious use of boldface
Austin Group Bug Tracker via austin-group-l at The Open Group
[Issue 8 drafts 0001676]: spurious use of boldface
Austin Group Bug Tracker via austin-group-l at The Open Group
make: -j documentation consistency enhancements
Andrew Pennebaker via austin-group-l at The Open Group
Re: make: -j documentation consistency enhancements
Robert Elz via austin-group-l at The Open Group
Re: make: -j documentation consistency enhancements
Roland Illig 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(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
[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
[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
[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
[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
[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
Earlier messages
Later messages