austin-group-l  

Messages by Thread

• • [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
  • [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
  • [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
  • [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
  • [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
  • 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
  • Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Geoff Clare via austin-group-l at The Open Group
  • Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* stef...@sdaoden.eu via austin-group-l at The Open Group
  • [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
  • [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
  • [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
  • [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
• Minutes of the 13th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• mailing list archive seems to stumble over HTML like text Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: mailing list archive seems to stumble over HTML like text Lawrence Velázquez via austin-group-l at The Open Group
  • Re: mailing list archive seems to stumble over HTML like text [SECURITY] Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: mailing list archive seems to stumble over HTML like text [SECURITY] Andrew Josey via austin-group-l at The Open Group
• [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
  • [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
  • [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
  • [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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • [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
  • [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
  • [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
  • [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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
• [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• [Online Pubs 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 6th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Fwd: [mikehaertel/minrx] Support new POSIX 2024 non-greedy repetition operators ?? *? and +?. (Issue #12) Niu Danny via austin-group-l at The Open Group
  • 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
• Can we no longer edit our own notes on bug tracker? Niu Danny via austin-group-l at The Open Group
  • Re: Can we no longer edit our own notes on bug tracker? Geoff Clare via austin-group-l at The Open Group
  • Re: Can we no longer edit our own notes on bug tracker? Niu Danny via austin-group-l at The Open Group
• [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
• I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• Minutes of the 27th February 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 27th February 2025 Teleconference - SIGFPE Fred J. Tydeman via austin-group-l at The Open Group
• [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro C via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Eric Blake via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn lanodan Monnier via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn lanodan Monnier via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn Monnier via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Lawrence Velázquez via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001911]: Clearify & consistently define "subexpression" for ERE. Austin Group Issue Tracker via austin-group-l at The Open Group
• Austin Group Aardvark is back ONLINE 23 Feb 2025 Mark Brown via austin-group-l at The Open Group
  • Re: Austin Group Aardvark is back ONLINE 23 Feb 2025 Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Austin Group Aardvark is back ONLINE 23 Feb 2025 Geoff Clare via austin-group-l at The Open Group
  • Re: Austin Group Aardvark is back ONLINE 23 Feb 2025 Steffen Nurpmeso via austin-group-l at The Open Group
• Aardvark account cleanup Mark Brown via austin-group-l at The Open Group
• [Test Project 0001909]: No e-mail received on any new Austin Group Issue Tracker updates. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Test Project 0001909]: No e-mail received on any new Austin Group Issue Tracker updates. Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Test Project 0001909]: No e-mail received on any new Austin Group Issue Tracker updates. Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 13th February 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Request for input on bug 1904 implementation behaviour for years prior to AD 1 Andrew Josey via austin-group-l at The Open Group
  • Re: Request for input on bug 1904 implementation behaviour for years prior to AD 1 Hans Åberg via austin-group-l at The Open Group
  • Re: Request for input on bug 1904 implementation behaviour for years prior to AD 1 Brooks Harris via austin-group-l at The Open Group
• Web site maintenance for austingroupbugs.net Feb 17-21 incl. Andrew Josey via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000598]: OH shading and new interfaces Austin Group Bug Tracker via austin-group-l at The Open Group
• Heads up: web site maintenance coming for austingroupbugs.net Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001906]: Mention O_CLOEXEC and O_CLOFORK in the unistd.h change history. Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001906]: Mention O_CLOEXEC and O_CLOFORK in the unistd.h change history. Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001906]: Mention O_CLOEXEC and O_CLOFORK in the unistd.h change history. Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001906]: Mention O_CLOEXEC and O_CLOFORK in the unistd.h change history. Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001906]: Mention O_CLOEXEC and O_CLOFORK in the unistd.h change history. Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001902]: THIS IS A TEST BUG - PLEASE IGNORE Austin Group Issue Tracker via austin-group-l at The Open Group
• [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001623]: website inaccessible via ipv6 Austin Group Issue Tracker via austin-group-l at The Open Group
  • PLEASE IGNORE Re: [Online Pubs 0001623]: website inaccessible via ipv6 Mark Brown via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000066]: sigaction/signal lists are different Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001905]: Conflicting text about async-signal-safety Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001905]: Conflicting text about async-signal-safety Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001905]: Conflicting text about async-signal-safety Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001905]: Conflicting text about async-signal-safety Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001904]: LC_TIME era start_date (and end_date) possibly mis-specified Austin Group Bug Tracker via austin-group-l at The Open Group
• [Online Pubs 0001904]: LC_TIME era start_date (and end_date) possibly mis-specified Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001904]: LC_TIME era start_date (and end_date) possibly mis-specified Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 30th January 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Re: (ogtgbase 5739) Request from the Austin Group: Call for objections (by Sep 22 2024) to standardising new APIs Eric Blake via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001903]: Default target description omits pattern rules Austin Group Bug Tracker via austin-group-l at The Open Group
• Minutes of the 23rd January 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000618]: require isatty and friends to set errno on failure Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0000618]: require isatty and friends to set errno on failure Austin Group Bug Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001902]: exec redirection and test -t Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001902]: exec redirection and test -t Austin Group Bug Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001902]: exec redirection and test -t Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 16th January 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
  • [test] Re: Minutes of the 16th January 2025 Teleconference G. Branden Robinson via austin-group-l at The Open Group
• awk and numeric value equal to an integer Vincent Lefevre via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0000516]: Calling longjmp() from a signal handler Austin Group Bug Tracker via austin-group-l at The Open Group
• exec redirection only portably defined for FDs <= 2 Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Lawrence Velázquez via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Oğuz via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Chet Ramey via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Martijn Dekker via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Lawrence Velázquez via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Lawrence Velázquez via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Geoff Clare via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Lawrence Velázquez via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Geoff Clare via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Geoff Clare via austin-group-l at The Open Group
  • Re: exec redirection only portably defined for FDs <= 2 Christoph Anton Mitterer via austin-group-l at The Open Group

• Earlier messages
• Later messages