| Time | Subject | # followups | From | 
|---|
| Mon, 30 Sep 2024 | 
| 22:52 | Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 22:46 | Re: [PATCH] Allow qualified filename (bar/foo) PAT | (2) | RVP | 
| 21:55 | Re: interactive shell detection in shrc | (1) | RVP | 
| 20:52 | Re: interactive shell detection in shrc | (3) | tlaronde | 
| 20:40 | Re: interactive shell detection in shrc | (2) | RVP | 
| 20:09 | Re: interactive shell detection in shrc | (3) | tlaronde | 
| 19:15 | Re: interactive shell detection in shrc | (1) | Greg A. Woods | 
| 14:37 | Re: posix_spawnp(3) not checking for empty file na | (0) | Martin Husemann | 
| 12:38 | [PATCH] include/paths.h comments about users | (0) | tlaronde | 
| 08:06 | Re: Fwd: Re: interactive shell detection in shrc | (1) | RVP | 
| 02:18 | Re: Fwd: Re: interactive shell detection in shrc | (0) | Mouse | 
| 01:50 | Re: Fwd: Re: interactive shell detection in shrc | (2) | Robert Elz | 
| 00:00 | Re: Fwd: Re: interactive shell detection in shrc | (0) | RVP | 
| Sun, 29 Sep 2024 | 
| 15:35 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | Edgar Fuß | 
| 15:13 | [PATCH] Allow qualified filename (bar/foo) PATH se | (1) | tlaronde | 
| 11:48 | posix_spawnp(3) not checking for empty file name | (1) | tlaronde | 
| 06:56 | Re: interactive shell detection in shrc | (1) | tlaronde | 
| Sat, 28 Sep 2024 | 
| 20:27 | Re: interactive shell detection in shrc | (1) | Greg A. Woods | 
| 12:04 | Re: PATH vs current dir and dir sure to be not exi | (0) | tlaronde | 
| 11:26 | Re: PATH vs current dir and dir sure to be not exi | (1) | Robert Elz | 
| 08:34 | PATH vs current dir and dir sure to be not existin | (1) | tlaronde | 
| 01:24 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | Jason Thorpe | 
| Fri, 27 Sep 2024 | 
| 23:29 | Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 22:44 | Re: interactive shell detection in shrc | (1) | Steffen Nurpmeso | 
| 22:35 | Re: interactive shell detection in shrc | (2) | Robert Elz | 
| 21:56 | Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 21:22 | Re: interactive shell detection in shrc | (1) | Greg A. Woods | 
| 20:51 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | Paul Goyette | 
| 19:10 | Re: interactive shell detection in shrc | (0) | Greg A. Woods | 
| 18:25 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | tlaronde | 
| 18:05 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | Mouse | 
| 16:28 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | Robert Elz | 
| 16:09 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 15:48 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (3) | Robert Elz | 
| 13:12 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 12:32 | Re: Symbols from new jemalloc not found | (0) | Ryo ONODERA | 
| 12:22 | Re: Symbols from new jemalloc not found | (0) | Rin Okuyama | 
| 11:52 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (2) | Robert Elz | 
| 10:26 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 01:29 | Re: interactive shell detection in shrc | (0) | Robert Elz | 
| 01:07 | Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 00:48 | Re: interactive shell detection in shrc | (0) | Robert Elz | 
| 00:23 | Re: interactive shell detection in shrc | (0) | RVP | 
| 00:14 | Re: interactive shell detection in shrc | (2) | Robert Elz | 
| 00:03 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (2) | Robert Elz | 
| Thu, 26 Sep 2024 | 
| 23:32 | Re: interactive shell detection in shrc | (4) | Steffen Nurpmeso | 
| 22:16 | Re: interactive shell detection in shrc | (2) | Greg A. Woods | 
| 21:39 | postinstall vs. obsolete libs | (0) | Valery Ushakov | 
| 14:10 | Re: Symbols from new jemalloc not found | (2) | Christos Zoulas | 
| 12:25 | Re: Symbols from new jemalloc not found | (0) | Ryo ONODERA | 
| 11:28 | Re: Symbols from new jemalloc not found | (1) | Taylor R Campbell | 
| 11:04 | Re: Symbols from new jemalloc not found | (0) | Ryo ONODERA | 
| 09:58 | PATH_OPT: allowing to search for qualified utiliti | (0) | tlaronde | 
| 07:19 | Re: Symbols from new jemalloc not found | (2) | Rin Okuyama | 
| 03:48 | Symbols from new jemalloc not found | (2) | Ryo ONODERA | 
| 00:45 | Re: etiquette for new failing test cases, followed | (0) | Greg Troxel | 
| Wed, 25 Sep 2024 | 
| 23:03 | Re: Fwd: Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 23:02 | Re: Fwd: Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 22:26 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | Robert Elz | 
| 21:25 | Re: etiquette for new failing test cases, followed | (1) | Taylor R Campbell | 
| 18:43 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 17:20 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (2) | tlaronde | 
| 17:02 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | Robert Elz | 
| 15:49 | Re: sh(1) and NUL | (2) | Robert Elz | 
| 14:44 | sh(1) and NUL | (1) | Thomas Klausner | 
| 14:04 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | Robert Elz | 
| 13:12 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 09:24 | Re: Fwd: Re: interactive shell detection in shrc | (0) | Robert Elz | 
| 07:17 | Re: Fwd: Re: interactive shell detection in shrc | (3) | Robert Elz | 
| 02:24 | Re: Fwd: Re: interactive shell detection in shrc | (0) | RVP | 
| Tue, 24 Sep 2024 | 
| 23:54 | Re: Fwd: Re: interactive shell detection in shrc | (2) | RVP | 
| 20:49 | Fwd: Re: interactive shell detection in shrc | (3) | Steffen Nurpmeso | 
| 19:54 | Re: interactive shell detection in shrc | (0) | Steffen Nurpmeso | 
| 18:23 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 17:19 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | Robert Elz | 
| 16:14 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | Robert Elz | 
| 15:46 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | Robert Elz | 
| 15:31 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 14:16 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (0) | tlaronde | 
| 13:09 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (1) | Greg Troxel | 
| 12:33 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (3) | tlaronde | 
| 11:55 | Re: sh(1) read: add LINE_MAX safeguard and "-n" op | (7) | Robert Elz | 
| 10:57 | sh(1) read: add LINE_MAX safeguard and "-n" option | (1) | tlaronde | 
| 09:33 | Re: interactive shell detection in shrc | (1) | Robert Elz | 
| 09:31 | Re: interactive shell detection in shrc | (0) | Robert Elz | 
| 00:15 | Re: interactive shell detection in shrc | (2) | Steffen Nurpmeso | 
| 00:07 | Re: interactive shell detection in shrc | (0) | Valery Ushakov | 
| Mon, 23 Sep 2024 | 
| 22:33 | Re: ed(1) as default editor in sh(1) | (0) | Greg Troxel | 
| 22:17 | ed(1) as default editor in sh(1) | (2) | tlaronde | 
| 22:01 | Re: interactive shell detection in shrc | (2) | Robert Elz | 
| 21:21 | Re: ed(1) as default editor in sh(1) | (0) | Valery Ushakov | 
| 21:10 | Re: interactive shell detection in shrc | (2) | Valery Ushakov | 
| 17:31 | Re: interactive shell detection in shrc | (2) | Robert Elz | 
| 09:16 | interactive shell detection in shrc | (1) | Valery Ushakov | 
| Sun, 22 Sep 2024 | 
| 18:33 | Re: sh(1): POSIX "Command Search and Execution" | (0) | tlaronde | 
| 17:35 | Re: sh(1): POSIX "Command Search and Execution" | (1) | David Holland | 
| 15:48 | Re: sh(1): POSIX "Command Search and Execution" | (0) | tlaronde | 
| 12:00 | Re: sh(1): POSIX "Command Search and Execution" | (1) | Robert Elz | 
| 11:53 | Re: sh(1): POSIX "Command Search and Execution" | (0) | tlaronde | 
| 11:47 | Re: sh(1): POSIX "Command Search and Execution" | (0) | RVP | 
| 11:38 | Re: sh(1): POSIX "Command Search and Execution" | (0) | tlaronde | 
| 11:07 | Re: sh(1): POSIX "Command Search and Execution" | (1) | Robert Elz | 
| 10:04 | Re: sh(1): POSIX "Command Search and Execution" | (3) | Robert Elz | 
| 07:19 | Re: sh(1): POSIX "Command Search and Execution" | (1) | tlaronde | 
| Sat, 21 Sep 2024 | 
| 21:39 | Re: sh(1): POSIX "Command Search and Execution" | (3) | Robert Elz | 
| 10:14 | Re: sh(1): POSIX "Command Search and Execution" | (0) | tlaronde | 
| Fri, 20 Sep 2024 | 
| 21:29 | Re: sh(1): POSIX "Command Search and Execution" | (2) | Robert Elz | 
| 19:36 | Re: etiquette for new failing test cases, followed | (0) | Roland Illig | 
| 17:12 | sh(1): POSIX "Command Search and Execution" | (2) | tlaronde | 
| 12:44 | Re: etiquette for new failing test cases, followed | (1) | Greg Troxel | 
| Thu, 19 Sep 2024 | 
| 18:52 | Re: etiquette for new failing test cases, followed | (1) | Roland Illig | 
| 13:35 | Re: etiquette for new failing test cases, followed | (0) | Martin Husemann | 
| 13:20 | etiquette for new failing test cases, followed by | (3) | Greg Troxel | 
| Mon, 16 Sep 2024 | 
| 12:06 | Re: mysterious remquo bug | (0) | Greg Troxel | 
| 05:54 | Re: mysterious remquo bug | (0) | Martin Husemann | 
| 05:07 | Re: mysterious remquo bug | (1) | Robert Elz | 
| 01:32 | Re: mysterious remquo bug | (0) | RVP | 
| 00:52 | Re: mysterious remquo bug | (0) | Greg Troxel | 
| Sun, 15 Sep 2024 | 
| 23:54 | mysterious remquo bug | (4) | Greg Troxel |