tech-userlevel  

Messages by Thread

• • Re: Symbols from new jemalloc not found Ryo ONODERA
  • Re: Symbols from new jemalloc not found Rin Okuyama
  • Re: Symbols from new jemalloc not found Taylor R Campbell
  • Re: Symbols from new jemalloc not found Ryo ONODERA
• sh(1) and NUL Thomas Klausner
  • Re: sh(1) and NUL Robert Elz
  • Re: sh(1) and NUL Thomas Klausner
  • Re: sh(1) and NUL Robert Elz
• sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Greg Troxel
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Robert Elz
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Mouse
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Paul Goyette
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Jason Thorpe
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" option Edgar Fuß
• ed(1) as default editor in sh(1) tlaronde
  • Re: ed(1) as default editor in sh(1) Valery Ushakov
  • Re: ed(1) as default editor in sh(1) Greg Troxel
• interactive shell detection in shrc Valery Ushakov
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Valery Ushakov
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc RVP
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc tlaronde
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc tlaronde
  • Re: interactive shell detection in shrc RVP
  • Re: interactive shell detection in shrc tlaronde
  • Re: interactive shell detection in shrc RVP
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc George Georgalis
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc George Georgalis
  • Re: interactive shell detection in shrc George Georgalis
  • Re: interactive shell detection in shrc tlaronde
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc Greg A. Woods
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Valery Ushakov
  • Re: interactive shell detection in shrc Robert Elz
  • Re: interactive shell detection in shrc Steffen Nurpmeso
  • Fwd: Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: Fwd: Re: interactive shell detection in shrc RVP
  • Re: Fwd: Re: interactive shell detection in shrc RVP
  • Re: Fwd: Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: Fwd: Re: interactive shell detection in shrc Robert Elz
  • Re: Fwd: Re: interactive shell detection in shrc Steffen Nurpmeso
  • Re: Fwd: Re: interactive shell detection in shrc RVP
  • Re: Fwd: Re: interactive shell detection in shrc Robert Elz
  • Re: Fwd: Re: interactive shell detection in shrc Mouse
  • Re: Fwd: Re: interactive shell detection in shrc RVP
  • Re: Fwd: Re: interactive shell detection in shrc Rhialto
  • Re: Fwd: Re: interactive shell detection in shrc RVP
  • Re: Fwd: Re: interactive shell detection in shrc RVP
  • Re: Fwd: Re: interactive shell detection in shrc Robert Elz
• sh(1): POSIX "Command Search and Execution" tlaronde
  • Re: sh(1): POSIX "Command Search and Execution" Robert Elz
  • Re: sh(1): POSIX "Command Search and Execution" tlaronde
  • Re: sh(1): POSIX "Command Search and Execution" Robert Elz
  • Re: sh(1): POSIX "Command Search and Execution" tlaronde
  • Re: sh(1): POSIX "Command Search and Execution" David Holland
  • Re: sh(1): POSIX "Command Search and Execution" tlaronde
  • Re: sh(1): POSIX "Command Search and Execution" Robert Elz
  • Re: sh(1): POSIX "Command Search and Execution" tlaronde
  • Re: sh(1): POSIX "Command Search and Execution" RVP
  • Re: sh(1): POSIX "Command Search and Execution" Robert Elz
  • Re: sh(1): POSIX "Command Search and Execution" tlaronde
  • Re: sh(1): POSIX "Command Search and Execution" Robert Elz
  • Re: sh(1): POSIX "Command Search and Execution" tlaronde
  • PATH_OPT: allowing to search for qualified utilities tlaronde
• etiquette for new failing test cases, followed by fix Greg Troxel
  • Re: etiquette for new failing test cases, followed by fix Martin Husemann
  • Re: etiquette for new failing test cases, followed by fix Roland Illig
  • Re: etiquette for new failing test cases, followed by fix Greg Troxel
  • Re: etiquette for new failing test cases, followed by fix Roland Illig
  • Re: etiquette for new failing test cases, followed by fix Taylor R Campbell
  • Re: etiquette for new failing test cases, followed by fix Greg Troxel
• mysterious remquo bug Greg Troxel
  • Re: mysterious remquo bug Greg Troxel
  • Re: mysterious remquo bug RVP
  • Re: mysterious remquo bug Robert Elz
  • Re: mysterious remquo bug Greg Troxel
  • Re: mysterious remquo bug Martin Husemann
• PR 44498 should probably be closed J Pipkin
  • Re: PR 44498 should probably be closed Mouse
  • Re: PR 44498 should probably be closed J Pipkin
• PR 39254 can be closed J Pipkin
  • Re: PR 39254 can be closed David Holland
• PR 57069 should not be open J Pipkin
• fix for PR 56138 J Pipkin
• test.1 -> "if file exists" -> "if pathname resolves to an existing directory entry" tlaronde
  • Re: test.1 -> "if file exists" -> "if pathname resolves to an existing directory entry" Robert Elz
  • Re: test.1 -> "if file exists" -> "if pathname resolves to an existing directory entry" Mouse
  • Re: test.1 -> "if file exists" -> "if pathname resolves to an existing directory entry" Robert Elz
  • Re: test.1 -> "if file exists" -> "if pathname resolves to an existing directory entry" tlaronde
• [PATCH] link.2: NetBSD doesn't allow link(2) to a directory, ever наб
  • Re: [PATCH] link.2: NetBSD doesn't allow link(2) to a directory, ever Valery Ushakov
• patch(1) max line length Emmanuel Dreyfus
  • Re: patch(1) max line length Robert Elz
  • Re: patch(1) max line length Emmanuel Dreyfus
  • Re: patch(1) max line length Crystal Kolipe
  • Re: patch(1) max line length Robert Elz
  • Re: patch(1) max line length Steffen Nurpmeso
  • Re: patch(1) max line length Steffen Nurpmeso
  • Re: patch(1) max line length Mouse
  • Re: patch(1) max line length Steffen Nurpmeso
• POSIX.2, IFS and echo command tlaronde
  • Re: POSIX.2, IFS and echo command наб
  • Re: POSIX.2, IFS and echo command tlaronde
  • Re: POSIX.2, IFS and echo command Greg A. Woods
  • Re: POSIX.2, IFS and echo command tlaronde
• compilers and unused args in functions Robert Elz
  • Re: compilers and unused args in functions Valery Ushakov
  • Re: compilers and unused args in functions Roland Illig
  • Re: compilers and unused args in functions Robert Elz
  • Re: compilers and unused args in functions Jörg Sonnenberger
  • Re: compilers and unused args in functions Robert Elz
  • Re: compilers and unused args in functions Mouse
  • Re: compilers and unused args in functions наб
  • Re: compilers and unused args in functions David Holland
  • Re: compilers and unused args in functions Greg A. Woods
• Adding functions to libutil, part 1 Reinoud Zandijk
  • Re: Adding functions to libutil, part 1 Michael van Elst
  • Re: Adding functions to libutil, part 1 Reinoud Zandijk
• Adding functions to libutil, part 2 Reinoud Zandijk
  • Re: Adding functions to libutil, part 2 Michael van Elst
  • Re: Adding functions to libutil, part 2 Reinoud Zandijk
  • Re: Adding functions to libutil, part 2 Michael van Elst
  • Re: Adding functions to libutil, part 2 Reinoud Zandijk
• awk gensub documentation Valery Ushakov
  • Re: awk gensub documentation Alistair Crooks
  • Re: awk gensub documentation Valery Ushakov
• Modifications on Tcsh. Matheus
• rpcgen -M missing foo_freeresult_N() signature? Anthony Mallet
• Fwd: git: fbfdf57d65be - main - Fix off-by-one bug in btpand Jessica Clarke
  • Re: Fwd: git: fbfdf57d65be - main - Fix off-by-one bug in btpand Iain Hibbert
• Proposal: include leap-seconds.list from tzdata Mallory Adams
  • Re: Proposal: include leap-seconds.list from tzdata Mallory Adams
  • Re: Proposal: include leap-seconds.list from tzdata Robert Elz
  • Re: Proposal: include leap-seconds.list from tzdata Mallory Adams
• (b)make: Outputting a huge variable value Edgar Fuß
  • Re: (b)make: Outputting a huge variable value Mouse
  • Re: (b)make: Outputting a huge variable value Edgar Fuß
  • Re: (b)make: Outputting a huge variable value RVP
  • Re: (b)make: Outputting a huge variable value Edgar Fuß
  • Re: (b)make: Outputting a huge variable value Roland Illig
  • Re: (b)make: Outputting a huge variable value Edgar Fuß
  • Re: (b)make: Outputting a huge variable value RVP
  • Re: (b)make: Outputting a huge variable value Roland Illig
• install -v Thomas Klausner
  • Re: install -v Jason Thorpe
• mktemp man page about mkdtemp(3) Aleksey Cheusov
  • Re: mktemp man page about mkdtemp(3) Roland Illig
• mkcsmapper.1 manpage and NOMAN Jeremy C. Reed
  • Re: mkcsmapper.1 manpage and NOMAN Jeremy C. Reed
  • Re: mkcsmapper.1 manpage and NOMAN Valery Ushakov
• MLINKS for hoststat.8 purgestat.8 to mailwrapper.8? Jeremy C. Reed
  • Re: MLINKS for hoststat.8 purgestat.8 to mailwrapper.8? Mouse

• Earlier messages
• Later messages