austin-group-l  

Messages by Thread

• [Issue 8 drafts 0001791]: tr: clarify encdings of non-characters bytes and proper encodings of the NUL byte and Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001791]: tr: clarify encdings of non-characters bytes and proper encodings of the NUL byte and Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 4th December 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 30th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 27th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001259]: wrong description for find -atime +7 example Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001789]: if command name contains slash, it cannot be arg0 for execl() Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 20th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001253]: clarify that "alternative time" means tm_isdst is positive Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001788]: The meaning of "Daylight Saving Time" should be clarified Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 16th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 13th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Approval of IEEE PAR Extension Request for P1003.1 Andrew Josey via austin-group-l at The Open Group
• Minutes of the 9th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 6th November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001787]: strcpy summary says it returns a pointer to the end of the result Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001787]: strcpy summary says it returns a pointer to the end of the result Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001787]: strcpy summary says it returns a pointer to the end of the result Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 2nd November 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0001787]: strcpy summary says it returns a pointer to the end of the result Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001787]: strcpy summary says it returns a pointer to the end of the result Austin Group Bug Tracker via austin-group-l at The Open Group
• Correction: Austin Group teleconference +1 888 974 9888 PIN 618 156 403 Single UNIX Specification via austin-group-l at The Open Group
• [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001786]: ed behavior on non-existing filename Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 30th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000248]: Fix the numerous filename/pathname processing errors in specification examples Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000248]: Fix the numerous filename/pathname processing errors in specification examples Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000248]: Fix the numerous filename/pathname processing errors in specification examples Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000248]: Fix the numerous filename/pathname processing errors in specification examples Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000351]: certain shell special built-ins should expand arguments in assignment context Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000351]: certain shell special built-ins should expand arguments in assignment context Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000351]: certain shell special built-ins should expand arguments in assignment context Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000351]: certain shell special built-ins should expand arguments in assignment context Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001393]: 'command' should not be treated as a declaration utility Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001393]: 'command' should not be treated as a declaration utility Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001393]: 'command' should not be treated as a declaration utility Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001393]: 'command' should not be treated as a declaration utility Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001535]: Poor description of declaration (all really) utility argument processing Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001535]: Poor description of declaration (all really) utility argument processing Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001535]: Poor description of declaration (all really) utility argument processing Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 26th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 26th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 23rd October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• system(NULL) overly restrictive? enh via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Oğuz via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Jonathan Wakely via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Oğuz via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Gabriel Ravier via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? enh via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Gabriel Ravier via austin-group-l at The Open Group
  • system(NULL) overly restrictive? Oğuz via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Gabriel Ravier via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Oğuz via austin-group-l at The Open Group
  • Re: system(NULL) overly restrictive? Robert Elz via austin-group-l at The Open Group
• [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues) Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 19th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• A philosophical question regarding shell vars & shell built-in utilities Robert Elz via austin-group-l at The Open Group
  • Re: A philosophical question regarding shell vars & shell built-in utilities Stephane Chazelas via austin-group-l at The Open Group
  • Re: A philosophical question regarding shell vars & shell built-in utilities Robert Elz via austin-group-l at The Open Group
  • Re: A philosophical question regarding shell vars & shell built-in utilities Geoff Clare via austin-group-l at The Open Group
  • Re: A philosophical question regarding shell vars & shell built-in utilities Stephane Chazelas via austin-group-l at The Open Group
  • Re: A philosophical question regarding shell vars & shell built-in utilities Robert Elz via austin-group-l at The Open Group
• Minutes of the 16th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• A volunteered effort on proof-reading rationale. DannyNiu via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001783]: This sentence from this section is discussing thread safety isn't it? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001783]: This sentence from this section is discussing thread safety isn't it? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001783]: This sentence from this section is discussing thread safety isn't it? Austin Group Bug Tracker via austin-group-l at The Open Group
• sh and .profile in Issue 7 Vincent Lefevre via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001782]: Standardize "pthread_yield"? Or change the example code? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001782]: Standardize "pthread_yield"? Or change the example code? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001782]: Standardize "pthread_yield"? Or change the example code? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001782]: Standardize "pthread_yield"? Or change the example code? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001782]: Standardize "pthread_yield"? Or change the example code? Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions? Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions? Austin Group Bug Tracker via austin-group-l at The Open Group
• Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
  • Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001780]: The punctuation is confusing/ambiguous Austin Group Bug Tracker via austin-group-l at The Open Group
• [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001779]: Standard does not say how much read should do if a read-only variable is given Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000657]: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 12th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 9th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 5th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 5th October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 2nd October 2023 Teleconference Andrew Josey via austin-group-l at The Open Group
• [Issue 8 drafts 0001778]: The read utility needs field splitting updates/corrections )and a little more) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001778]: The read utility needs field splitting updates/corrections )and a little more) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001778]: The read utility needs field splitting updates/corrections )and a little more) Austin Group Bug Tracker via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001778]: The read utility needs field splitting updates/corrections )and a little more) Robert Elz via austin-group-l at The Open Group
  • [Issue 8 drafts 0001778]: The read utility needs field splitting updates/corrections )and a little more) Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001778]: The read utility needs field splitting updates/corrections )and a little more) Austin Group Bug Tracker via austin-group-l at The Open Group

• Earlier messages
• Later messages