austin-group-l  

Messages by Thread

• Minutes of the 15th November 2018 Teleconference Andrew Josey
• Where can I find information on "binding to system-assigned port" Danny Niu
  • Re: Where can I find information on "binding to system-assigned port" Shware Systems
• Minutes of the 8th November 2018 Teleconference Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001215]: XSI shading on text about abnormal termination with actions Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001215]: XSI shading on text about abnormal termination with actions Austin Group Bug Tracker
• Minutes of the 1st November 2018 Teleconference Andrew Josey
  • Re: Minutes of the 1st November 2018 Teleconference Robert Elz
• Obsolecense of SCCS Drew DeVault
• Unnamed shared memory objects Simon Ser
  • Re: Unnamed shared memory objects Simon Ser
• Minutes of the 25th October 2018 Teleconference Andrew Josey
• Re: [1003.1(2016)/Issue7+TC2 0001141]: Add WCOREDUMP(stat) to sys/wait.h Robert Elz
• Minutes of the 11th October 2018 Teleconference Andrew Josey
  • Minutes of the 11th October 2018 Teleconference Andrew Josey
  • Minutes of the 18th October 2018 Teleconference Andrew Josey
• Minutes of the 4th October 2018 Teleconference Andrew Josey
• [1003.1(2013)/Issue7+TC1 0001137]: problems with numbered and unnumbered conversion specifications Austin Group Bug Tracker
  • [1003.1(2013)/Issue7+TC1 0001137]: problems with numbered and unnumbered conversion specifications Austin Group Bug Tracker
  • [1003.1(2013)/Issue7+TC1 0001137]: problems with numbered and unnumbered conversion specifications Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001214]: remove claim about pthread_kill behavior when sig is 0? Austin Group Bug Tracker
• Mantis account setup Andrew Josey
• Minutes of the 27th September 2018 Teleconference Andrew Josey
• More Interpretations starting a 30 day final review Andrew Josey
• Interpretations starting a 30 day final review Andrew Josey
  • Interpretations starting a 30 day final review Andrew Josey
  • Interpretations starting a 30 day final review Andrew Josey
• pthread_kill with signal 0 enh
  • Re: pthread_kill with signal 0 enh
• [1003.1(2016)/Issue7+TC2 0001213]: Typos in character constants in strtod() APPLICATON USAGE example. Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001213]: Typos in character constants in strtod() APPLICATON USAGE example. Austin Group Bug Tracker
• Typos in strtod documentation Oleksii Vilchanskyi
  • Re: Typos in strtod documentation Don Cragun
  • Re: Typos in strtod documentation Oleksii Vilchanskyi
  • Re: Typos in strtod documentation Don Cragun
• Several questions about $'...' Harald van Dijk
  • Re: Several questions about $'...' Steffen Nurpmeso
  • Re: Several questions about $'...' Robert Elz
  • Re: Several questions about $'...' Steffen Nurpmeso
  • Re: Several questions about $'...' Robert Elz
  • Re: Several questions about $'...' Steffen Nurpmeso
  • Re: Several questions about $'...' Stephane Chazelas
  • Re: Several questions about $'...' Harald van Dijk
  • Re: Several questions about $'...' Chet Ramey
• [1003.1(2016)/Issue7+TC2 0001212]: Enhance trap command Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Geoff Clare
  • [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001211]: "trap" (with no args) specification does not match reality Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0000621]: Ambiguos requirements for trap on EXIT Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001210]: FTW_MOUNT and symbolic links to directories on other file systems Austin Group Bug Tracker
• Minutes of the 20th September 2018 Teleconference Andrew Josey
• Minutes of the 13th September 2018 Teleconference Andrew Josey
  • Re: Minutes of the 13th September 2018 Teleconference Bruce Evans
  • Bug 1133 find -xdev (was: Minutes of the 13th September 2018 Teleconference) Geoff Clare
  • Re: Bug 1133 find -xdev (was: Minutes of the 13th September 2018 Teleconference) Joerg Schilling
  • Re: Bug 1133 find -xdev (was: Minutes of the 13th September 2018 Teleconference) Geoff Clare
  • Re: Bug 1133 find -xdev (was: Minutes of the 13th September 2018 Teleconference) Joerg Schilling
  • Re: Bug 1133 find -xdev (was: Minutes of the 13th September 2018 Teleconference) Geoff Clare
• [1003.1(2016)/Issue7+TC2 0001135]: Is "all data" when len is 0 a snapshot of file's length? Austin Group Bug Tracker
• [1003.1(2004)/Issue 6 0000316]: fprintf EOVERFLOW Austin Group Bug Tracker
• [1003.1(2004)/Issue 6 0000315]: sem_post maximum number of semaphores Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0000411]: adding atomic FD_CLOEXEC support Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0000415]: add SEEK_HOLE, SEEK_DATA to lseek Austin Group Bug Tracker
• [1003.1(2008)/Issue 7 0001209]: printf example for numeric value of character is wrong Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001209]: printf example for numeric value of character is wrong Austin Group Bug Tracker
  • [1003.1(2008)/Issue 7 0001209]: printf example for numeric value of character is wrong Austin Group Bug Tracker
• Minutes of the 6th September 2018 Teleconference Andrew Josey
  • Re: Minutes of the 6th September 2018 Teleconference enh
• Re: [RFC/PATCH glibc 0/2] setting working dir in posix_spawn() Eric Blake
  • Re: [RFC/PATCH glibc 0/2] setting working dir in posix_spawn() Eric Blake
• [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001208]: calling chdir as part of posix_spawn Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0000900]: add qsort_r Austin Group Bug Tracker
  • [1003.1(2013)/Issue7+TC1 0000900]: add qsort_r Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0000981]: Remove oudated set -o nolog Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001207]: "set -o option" should be mandatory, not UP Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001207]: "set -o option" should be mandatory, not UP Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001207]: "set -o option" should be mandatory, not UP Austin Group Bug Tracker
• Status of pipefail for standardization Drew DeVault
  • Re: Status of pipefail for standardization Geoff Clare
  • Re: Status of pipefail for standardization Drew DeVault
  • Re: Status of pipefail for standardization Drew DeVault
  • Re: Status of pipefail for standardization Geoff Clare
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Geoff Clare
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Geoff Clare
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Chet Ramey
  • Re: Status of pipefail for standardization Geoff Clare
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Chet Ramey
  • Re: Status of pipefail for standardization Siteshwar Vashisht
  • Re: Status of pipefail for standardization Joerg Schilling
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Chet Ramey
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Chet Ramey
  • Re: Status of pipefail for standardization Robert Elz
  • Re: Status of pipefail for standardization Joerg Schilling
  • Re: Status of pipefail for standardization Siteshwar Vashisht
  • Re: Status of pipefail for standardization Joerg Schilling
  • Re: Status of pipefail for standardization Siteshwar Vashisht
  • Re: Status of pipefail for standardization Joerg Schilling
  • Re: Status of pipefail for standardization Robert Elz
• [1003.1(2016)/Issue7+TC2 0001206]: The echo that supports -n is Bell Labs Unix echo, not "BSD echo" Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001206]: The echo that supports -n is Bell Labs Unix echo, not "BSD echo" Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001205]: Incorrect specification of printf %% Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001205]: Incorrect specification of printf %% Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001205]: Incorrect specification of printf %% Austin Group Bug Tracker
• Minutes of the 30th August 2018 Teleconference Andrew Josey
• [1003.1(2016)/Issue7+TC2 0001204]: Vague wording as to the validity of s/RE command without trailing delimiter and replacement Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001203]: fcntl return value inconsistent wording Austin Group Bug Tracker
• C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Tom Cherry
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Tom Cherry
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Daniel Eischen
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Tom Cherry
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads enh
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Daniel Eischen
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Tom Cherry
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Mike Crowe
  • Re: C++ condition_variable and timed_mutex with steady_clock and pthreads Daniel Eischen
  • Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads) Mike Crowe
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads) Daniel Eischen
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads) Mike Crowe
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads) Mark Harris
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads) Tom Cherry
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads) Mike Crowe
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs Mike Crowe
  • Re: Adding a clockid_t parameter to functions that accept absolute timespecs Daniel Eischen
• [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Austin Group Bug Tracker
  • Re: [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Robert Elz
  • Re: [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Robert Elz
  • [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001202]: printf %.Nb with \c in arg (more than N chars into arg) behaviour unclear Austin Group Bug Tracker
• New UNIX Certification News - Oracle Corporation Andrew Josey
  • Re: New UNIX Certification News - Oracle Corporation Stephane Chazelas
  • Re: New UNIX Certification News - Oracle Corporation Alan Coopersmith
  • Re: New UNIX Certification News - Oracle Corporation Geoff Clare
• Draft minutes of the 23rd August 2018 Teleconference Geoff Clare
• [1003.1(2013)/Issue7+TC1 0001201]: Atomicity requirements for sigsuspend Austin Group Bug Tracker
  • [1003.1(2013)/Issue7+TC1 0001201]: Atomicity requirements for sigsuspend Austin Group Bug Tracker
• [1003.1(2016)/Issue7+TC2 0001200]: Mismatch in parameter names in ELOOP entry in ERRORS section on various pages Austin Group Bug Tracker
• [1003.1(2013)/Issue7+TC1 0001200]: Mismatch in parameter names in ELOOP entry in ERRORS section on various pages Austin Group Bug Tracker
  • [1003.1(2013)/Issue7+TC1 0001200]: Mismatch in parameter names in ELOOP entry in ERRORS section on various pages Austin Group Bug Tracker
• Minutes of the 16th August 2018 Teleconference Andrew Josey
• what variables are affected by the "allexport" shell option? Stephane Chazelas
  • Re: what variables are affected by the "allexport" shell option? Robert Elz
  • Re: what variables are affected by the "allexport" shell option? Chet Ramey
  • Re: what variables are affected by the "allexport" shell option? Robert Elz
• exit status of ! break (in sh) Robert Elz
  • Re: exit status of ! break (in sh) Stephane Chazelas
  • RE: exit status of ! break (in sh) Shware Systems
  • Re: exit status of ! break (in sh) Stephane Chazelas
  • Re: exit status of ! break (in sh) Joerg Schilling
  • Re: exit status of ! break (in sh) Robert Elz
  • Re: exit status of ! break (in sh) Joerg Schilling
  • Re: exit status of ! break (in sh) Stephane CHAZELAS
  • Re: exit status of ! break (in sh) Joerg Schilling
  • Re: exit status of ! break (in sh) Robert Elz
  • Re: exit status of ! break (in sh) Robert Elz
  • Re: exit status of ! break (in sh) Jilles Tjoelker
  • Re: exit status of ! break (in sh) Robert Elz
  • Re: exit status of ! break (in sh) Joerg Schilling
• [1003.1(2016)/Issue7+TC2 0001199]: strfmon, if standards compliant, produces highly misleading results Austin Group Bug Tracker
  • [1003.1(2016)/Issue7+TC2 0001199]: strfmon, if standards compliant, produces highly misleading results Austin Group Bug Tracker
• Draft minutes of the 9th August 2018 Teleconference Geoff Clare

• Earlier messages