Messages by Date
-
2023/11/22
[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
-
2023/11/22
[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
-
2023/11/22
[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
-
2023/11/21
[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
-
2023/11/21
[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
-
2023/11/21
[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
-
2023/11/21
[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
-
2023/11/21
[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
-
2023/11/21
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/21
[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
-
2023/11/20
Minutes of the 20th November 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/20
[Issue 8 drafts 0001776]: find -newer any symlinks
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/20
[Issue 8 drafts 0001776]: find -newer any symlinks
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/20
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/20
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/20
[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
-
2023/11/20
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/20
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/20
[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
-
2023/11/20
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/19
[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
-
2023/11/19
[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
-
2023/11/19
[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
-
2023/11/17
[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
-
2023/11/17
Minutes of the 16th November 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/16
[1003.1(2016/18)/Issue7+TC2 0001775]: si_addr description confusingly over-specific
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/16
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/16
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/14
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/14
[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
-
2023/11/14
[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
-
2023/11/14
[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
-
2023/11/14
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/14
Minutes of the 13th November 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/14
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/13
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/13
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/13
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/13
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/10
Approval of IEEE PAR Extension Request for P1003.1
Andrew Josey via austin-group-l at The Open Group
-
2023/11/10
Minutes of the 9th November 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/09
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/08
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/08
Minutes of the 6th November 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/06
[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
-
2023/11/06
[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
-
2023/11/04
Minutes of the 2nd November 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/03
[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
-
2023/11/02
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/02
Correction: Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/11/02
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/02
[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
-
2023/11/02
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/02
[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
-
2023/11/02
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/02
[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
-
2023/11/02
[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
-
2023/11/02
[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
-
2023/11/02
[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
-
2023/11/02
[Issue 8 drafts 0001786]: ed behavior on non-existing filename
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/02
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/02
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/11/01
Minutes of the 30th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/11/01
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/30
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/30
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/30
[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
-
2023/10/30
[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
-
2023/10/30
[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
-
2023/10/30
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/30
[Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
Re: A philosophical question regarding shell vars & shell built-in utilities
Robert Elz via austin-group-l at The Open Group
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[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
-
2023/10/27
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
[Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/27
Re: Minutes of the 26th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/27
Minutes of the 26th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/27
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/26
Re: system(NULL) overly restrictive?
Oğuz via austin-group-l at The Open Group
-
2023/10/26
Re: system(NULL) overly restrictive?
Gabriel Ravier via austin-group-l at The Open Group
-
2023/10/26
Re: system(NULL) overly restrictive?
Robert Elz via austin-group-l at The Open Group
-
2023/10/26
system(NULL) overly restrictive?
Oğuz via austin-group-l at The Open Group
-
2023/10/25
Re: system(NULL) overly restrictive?
Gabriel Ravier via austin-group-l at The Open Group
-
2023/10/25
Re: system(NULL) overly restrictive?
enh via austin-group-l at The Open Group
-
2023/10/25
Re: system(NULL) overly restrictive?
Gabriel Ravier via austin-group-l at The Open Group
-
2023/10/24
Re: system(NULL) overly restrictive?
Oğuz via austin-group-l at The Open Group
-
2023/10/24
Minutes of the 23rd October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/24
Re: system(NULL) overly restrictive?
Jonathan Wakely via austin-group-l at The Open Group
-
2023/10/23
Re: A philosophical question regarding shell vars & shell built-in utilities
Stephane Chazelas via austin-group-l at The Open Group
-
2023/10/23
Re: system(NULL) overly restrictive?
Oğuz via austin-group-l at The Open Group
-
2023/10/23
system(NULL) overly restrictive?
enh via austin-group-l at The Open Group
-
2023/10/23
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/23
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/23
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/23
Re: A philosophical question regarding shell vars & shell built-in utilities
Geoff Clare via austin-group-l at The Open Group
-
2023/10/23
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/21
[Issue 8 drafts 0001784]: getopts specification needs fixing (multiple issues)
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/21
Re: A philosophical question regarding shell vars & shell built-in utilities
Robert Elz via austin-group-l at The Open Group
-
2023/10/21
Re: A philosophical question regarding shell vars & shell built-in utilities
Stephane Chazelas via austin-group-l at The Open Group
-
2023/10/20
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/20
Minutes of the 19th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/20
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/19
A philosophical question regarding shell vars & shell built-in utilities
Robert Elz via austin-group-l at The Open Group
-
2023/10/19
[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
-
2023/10/19
[1003.1(2008)/Issue 7 0000251]: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/19
[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
-
2023/10/18
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/18
Minutes of the 16th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/17
A volunteered effort on proof-reading rationale.
DannyNiu via austin-group-l at The Open Group
-
2023/10/17
[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
-
2023/10/17
[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
-
2023/10/17
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/17
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/17
sh and .profile in Issue 7
Vincent Lefevre via austin-group-l at The Open Group
-
2023/10/17
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/17
[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
-
2023/10/17
[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
-
2023/10/17
[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
-
2023/10/17
[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
-
2023/10/16
Interpretation for a 30 day review
Andrew Josey via austin-group-l at The Open Group
-
2023/10/16
[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
-
2023/10/16
[1003.1(2016/18)/Issue7+TC2 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/16
[Issue 8 drafts 0001780]: The punctuation is confusing/ambiguous
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/16
[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
-
2023/10/13
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/13
Minutes of the 12th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/12
[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
-
2023/10/12
[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
-
2023/10/12
[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
-
2023/10/11
[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
-
2023/10/11
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/11
Minutes of the 9th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/11
[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
-
2023/10/10
[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
-
2023/10/10
[Issue 8 drafts 0001771]: support or reserve %q as printf-utility format specifier
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/10
[Issue 8 drafts 0001649]: Field splitting is woefully under specified, and in places, simply wrong
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/10
[Issue 8 drafts 0001649]: Field splitting is woefully under specified, and in places, simply wrong
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/10
[1003.1(2016/18)/Issue7+TC2 0001406]: clarification of SEEK_END when current pointer doesn't match buffer size
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/10
[1003.1(2008)/Issue 7 0000689]: Possibly unintended allowance for stdio deadlock
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/10
[1003.1(2016/18)/Issue7+TC2 0001273]: glob()'s GLOB_ERR/errfunc and non-directory files
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/09
Re: Minutes of the 5th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/06
[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
-
2023/10/06
Minutes of the 5th October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/06
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/06
[Issue 8 drafts 0001771]: support or reserve %q as printf-utility format specifier
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/05
[Issue 8 drafts 0001771]: support or reserve %q as printf-utility format specifier
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/05
[Issue 8 drafts 0001771]: support or reserve %q as printf-utility format specifier
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/05
[Issue 8 drafts 0001771]: support or reserve %q as printf-utility format specifier
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/05
[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
-
2023/10/05
[Issue 8 drafts 0001771]: support or reserve %q as printf-utility format specifier
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/05
[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
-
2023/10/05
[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
-
2023/10/05
[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
-
2023/10/04
[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
-
2023/10/04
Minutes of the 2nd October 2023 Teleconference
Andrew Josey via austin-group-l at The Open Group
-
2023/10/04
[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
-
2023/10/03
[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
-
2023/10/03
[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
-
2023/10/03
[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
-
2023/10/03
[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
-
2023/10/02
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
Single UNIX Specification via austin-group-l at The Open Group
-
2023/10/02
[Issue 8 drafts 0001649]: Field splitting is woefully under specified, and in places, simply wrong
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/02
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
-
2023/10/02
[Issue 8 drafts 0001649]: Field splitting is woefully under specified, and in places, simply wrong
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/02
[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
-
2023/10/02
[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
-
2023/10/02
[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
-
2023/10/02
[1003.1(2008)/Issue 7 0000456]: mandate binary mode of fmemopen
Austin Group Bug Tracker via austin-group-l at The Open Group
-
2023/10/02
Re: [Issue 8 drafts 0001649]: Field splitting is woefully under specified, and in places, simply wrong
Robert Elz via austin-group-l at The Open Group
-
2023/10/02
[1003.1(2016/18)/Issue7+TC2 0001273]: glob()'s GLOB_ERR/errfunc and non-directory files
Austin Group Bug Tracker via austin-group-l at The Open Group