austin-group-l (original) (raw)

Messages by Date

• 2025/04/29 Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/29 [1003.1(2016/18)/Issue7+TC2 0001793]: Streamline US-ASCII character set name Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/29 [Issue 8 drafts 0001792]: Example 7 needs to use find's -H option Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/29 [1003.1(2016/18)/Issue7+TC2 0001790]: More info on *ALT* constants Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/29 [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
• 2025/04/29 [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
• 2025/04/29 [Issue 8 drafts 0001785]: Conflict in specification of processing of declaration utilities Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/29 [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/29 [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/29 [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/28 [1003.1(2024)/Issue8 0001921]: A future C compilation interface needs to support "#embed" Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/28 [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/28 Re: (1920) splitting by bytes in UTF-8 Stephane Chazelas via austin-group-l at The Open Group
• 2025/04/28 Re: Issue 1920 Stephane Chazelas via austin-group-l at The Open Group
• 2025/04/28 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/28 [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/28 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/28 Minutes of the 24th April 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/04/28 Issue 1920 Chet Ramey via austin-group-l at The Open Group
• 2025/04/27 Austin Group WEBEX +1-408-792-6300 PIN 668 216 233 Single UNIX Specification via austin-group-l at The Open Group
• 2025/04/27 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/26 Re: PDF index^WToC issue Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/25 Re: PDF index^WToC issue Thorsten Glaser via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2024)/Issue8 0001918]: c16rtomb, c32rtomb Description Incorrectly References mbrtoc16() in Description Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/24 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/23 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/23 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/23 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/23 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/22 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/22 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/22 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/21 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/21 [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/19 [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/18 [1003.1(2024)/Issue8 0001918]: c16rtomb, c32rtomb Description Incorrectly References mbrtoc16() in Description Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/17 Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
• 2025/04/17 [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/15 Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/15 Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
• 2025/04/15 Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/15 Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
• 2025/04/15 [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/11 Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/11 Re: Call for input on 2.6.5 field splitting (bug 1915) Chet Ramey via austin-group-l at The Open Group
• 2025/04/11 Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/11 Re: Call for input on 2.6.5 field splitting (bug 1915) Chet Ramey via austin-group-l at The Open Group
• 2025/04/11 Minutes of the 10th April 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/04/11 Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/04/10 Austin Group WEBEX +1-408-792-6300 PIN 668 216 233 Single UNIX Specification via austin-group-l at The Open Group
• 2025/04/10 Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
• 2025/04/05 [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/05 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/04/05 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/04/05 [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/05 Re: Interpretation for a 30 day review (1857 revised) Geoff Clare via austin-group-l at The Open Group
• 2025/04/05 [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/05 [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/05 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/04 Formatting error for online issue 8 HTML docs, for make utility Wayne Pollock via austin-group-l at The Open Group
• 2025/04/04 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/04/04 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/04/04 Minutes of the 27th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/04/03 Minutes of the 3rd April 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/04/03 Austin Group WEBEX +1-408-792-6300 PIN 668 216 233 Single UNIX Specification via austin-group-l at The Open Group
• 2025/04/01 [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/04/01 Austin Group WEBEX +1-408-792-6300 PIN 668 216 233 Single UNIX Specification via austin-group-l at The Open Group
• 2025/04/01 Austin Group WEBEX +1-408-792-6300 PIN 668 216 233 Single UNIX Specification via austin-group-l at The Open Group
• 2025/03/31 the speed_t interfaces are inadequate (bug 1916) Andrew Josey via austin-group-l at The Open Group
• 2025/03/31 Call for input on 2.6.5 field splitting (bug 1915) Andrew Josey via austin-group-l at The Open Group
• 2025/03/27 [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/27 [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/27 [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/27 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/03/26 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/03/25 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/24 [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/24 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/03/24 Minutes of the 20th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/03/22 [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/21 [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/21 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/21 Re: Interpretation for a 30 day review (1857 revised) Niu Danny via austin-group-l at The Open Group
• 2025/03/21 Interpretation for a 30 day review (1857 revised) Andrew Josey via austin-group-l at The Open Group
• 2025/03/20 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/20 [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/20 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/20 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/20 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/20 Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/20 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/20 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• 2025/03/20 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
• 2025/03/19 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Lawrence Velázquez via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/03/18 Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/03/18 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/03/18 [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• 2025/03/18 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/03/18 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/18 [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/18 [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/18 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/17 [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/17 Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/03/15 Minutes of the 13th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/03/15 [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 Interpretation for a 30 day review Andrew Josey via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 Re: mailing list archive seems to stumble over HTML like text [SECURITY] Andrew Josey via austin-group-l at The Open Group
• 2025/03/13 [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/13 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• 2025/03/12 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/12 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/03/12 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
• 2025/03/12 Re: mailing list archive seems to stumble over HTML like text [SECURITY] Christoph Anton Mitterer via austin-group-l at The Open Group
• 2025/03/12 Re: exec redirection only portably defined for FDs <= 2 Geoff Clare via austin-group-l at The Open Group
• 2025/03/12 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/11 Re: mailing list archive seems to stumble over HTML like text Lawrence Velázquez via austin-group-l at The Open Group
• 2025/03/11 mailing list archive seems to stumble over HTML like text Christoph Anton Mitterer via austin-group-l at The Open Group
• 2025/03/11 Re: exec redirection only portably defined for FDs <= 2 Christoph Anton Mitterer via austin-group-l at The Open Group
• 2025/03/11 [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/11 Re: exec redirection only portably defined for FDs <= 2 Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/03/11 Re: exec redirection only portably defined for FDs <= 2 Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/03/11 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/11 Re: exec redirection only portably defined for FDs <= 2 Christoph Anton Mitterer via austin-group-l at The Open Group
• 2025/03/11 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• 2025/03/11 [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/11 [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/11 Re: exec redirection only portably defined for FDs <= 2 Geoff Clare via austin-group-l at The Open Group
• 2025/03/11 Re: exec redirection only portably defined for FDs <= 2 Geoff Clare via austin-group-l at The Open Group
• 2025/03/10 [Online Pubs 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/09 Minutes of the 6th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• 2025/03/09 Austin Group WEBEX +1-408-792-6300 PIN 668 216 233 Single UNIX Specification via austin-group-l at The Open Group
• 2025/03/09 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
• 2025/03/08 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Lawrence Velázquez via austin-group-l at The Open Group
• 2025/03/08 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
• 2025/03/08 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn Monnier via austin-group-l at The Open Group
• 2025/03/08 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/08 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
• 2025/03/08 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/08 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn lanodan Monnier via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
• 2025/03/07 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn lanodan Monnier via austin-group-l at The Open Group
• 2025/03/07 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Eric Blake via austin-group-l at The Open Group
• 2025/03/07 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/07 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
• 2025/03/06 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
• 2025/03/06 Re: Can we no longer edit our own notes on bug tracker? Niu Danny via austin-group-l at The Open Group
• 2025/03/06 Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro C via austin-group-l at The Open Group
• 2025/03/06 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/06 Re: Can we no longer edit our own notes on bug tracker? Geoff Clare via austin-group-l at The Open Group
• 2025/03/06 [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/06 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/06 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• 2025/03/06 Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• 2025/03/06 [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/06 Re: Fwd: [mikehaertel/minrx] Support new POSIX 2024 non-greedy repetition operators ?? *? and +?. (Issue #12) Geoff Clare via austin-group-l at The Open Group
• 2025/03/06 [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/05 Fwd: [mikehaertel/minrx] Support new POSIX 2024 non-greedy repetition operators ?? *? and +?. (Issue #12) Niu Danny via austin-group-l at The Open Group
• 2025/03/05 [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Austin Group Issue Tracker via austin-group-l at The Open Group
• 2025/03/05 Can we no longer edit our own notes on bug tracker? Niu Danny via austin-group-l at The Open Group
• 2025/03/04 Re: [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Niu Danny via austin-group-l at The Open Group
• 2025/03/04 Re: [1003.1(2024)/Issue8 0001857]: Several problems with the new "lazy" regex quantifier. Steffen Nurpmeso via austin-group-l at The Open Group
• 2025/03/04 [1003.1(2013)/Issue7+TC1 0000793]: Regular Expressions: add REG_MINIMAL and a minimum repitition modifier Austin Group Issue Tracker via austin-group-l at The Open Group
• Earlier messages