| Time | Subject | # followups | From |
|---|
| Fri, 30 Jun 2023 |
| 19:03 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(0) |
Martin Neitzel |
| 17:37 |
Trivial program size inflation |
(3) |
Mouse |
| 17:28 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
Robert Elz |
| 15:51 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
tlaronde |
| 15:37 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(2) |
David Holland |
| 15:32 |
Re: old style tail(1) options and bin/57483 |
(0) |
Robert Elz |
| 12:37 |
old style tail(1) options and bin/57483 |
(2) |
Valery Ushakov |
| Thu, 29 Jun 2023 |
| 07:47 |
[CODE] inetd OK |
(0) |
tlaronde |
| 00:10 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(0) |
RVP |
| Wed, 28 Jun 2023 |
| 18:37 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(0) |
наб |
| 17:20 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(0) |
tlaronde |
| 17:15 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(0) |
tlaronde |
| 17:12 |
missing long double functions in netbsd-9 |
(0) |
Greg Troxel |
| 17:10 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(0) |
tlaronde |
| 16:59 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
Roland Illig |
| 16:46 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(2) |
Mouse |
| 16:32 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(2) |
tlaronde |
| 16:24 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
RVP |
| 16:06 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(2) |
Martin Husemann |
| 15:59 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
tlaronde |
| 15:26 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
Martin Husemann |
| 15:02 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(2) |
tlaronde |
| 13:10 |
Re: printf(1), sh(1), POSIX.2 and octal escape seq |
(1) |
RVP |
| 10:58 |
printf(1), sh(1), POSIX.2 and octal escape sequenc |
(2) |
tlaronde |
| Tue, 27 Jun 2023 |
| 17:53 |
[RFC] String Auxiliary Processor: a... SAP! |
(0) |
tlaronde |
| 14:50 |
[CODE] inetd(8) |
(0) |
tlaronde |
| Mon, 26 Jun 2023 |
| 15:09 |
inetd(8): final version tomorrow |
(0) |
tlaronde |
| Fri, 23 Jun 2023 |
| 10:33 |
Re: vi(1) one line crasher |
(0) |
tlaronde |
| Thu, 22 Jun 2023 |
| 22:56 |
Re: vi(1) one line crasher |
(1) |
Martin Neitzel |
| 19:24 |
Re: vi(1) one line crasher |
(0) |
tlaronde |
| 18:54 |
Re: vi(1) one line crasher |
(1) |
Martin Husemann |
| 18:52 |
Re: vi(1) one line crasher |
(1) |
Martin Husemann |
| 18:48 |
vi(1) one line crasher |
(2) |
tlaronde |
| 18:29 |
Re: vi(1) one line crasher |
(0) |
tlaronde |
| 18:00 |
Re: vi(1) one line crasher |
(1) |
Martin Neitzel |
| 16:49 |
Re: vi(1) one line crasher |
(0) |
tlaronde |
| 16:40 |
Re: vi(1) one line crasher |
(1) |
Martin Husemann |
| 16:23 |
vi(1) one line crasher |
(2) |
tlaronde |
| Tue, 20 Jun 2023 |
| 07:12 |
Re: [CODE] inetd |
(0) |
tlaronde |
| Mon, 19 Jun 2023 |
| 17:35 |
[CODE] inetd |
(1) |
tlaronde |
| Thu, 15 Jun 2023 |
| 21:12 |
Re: inetd(8): cmdif as builtin |
(0) |
Luke Mewburn |
| Tue, 13 Jun 2023 |
| 01:23 |
Re: inetd(8): cmdif as builtin |
(0) |
Mouse |
| Mon, 12 Jun 2023 |
| 22:15 |
Re: inetd(8): cmdif as builtin |
(2) |
Brett Lymn |
| Fri, 09 Jun 2023 |
| 20:20 |
Re: inetd(8): cmdif as builtin |
(0) |
tlaronde |
| 19:48 |
Re: inetd(8): cmdif as builtin |
(1) |
Mouse |
| 17:10 |
Re: inetd(8): cmdif as builtin |
(1) |
tlaronde |
| 12:47 |
Re: inetd(8): cmdif as builtin |
(2) |
Mouse |
| 11:18 |
inetd(8): cmdif as builtin |
(1) |
tlaronde |
| Thu, 08 Jun 2023 |
| 15:37 |
[CODE] inetd |
(0) |
tlaronde |
| Mon, 05 Jun 2023 |
| 15:23 |
Re: How to profile NSS code? |
(0) |
Taylor R Campbell |
| 15:01 |
How to profile NSS code? |
(1) |
Emmanuel Dreyfus |
| 13:17 |
inetd(8): code tomorrow or, at worst, on Thursday |
(0) |
tlaronde |
| Sun, 04 Jun 2023 |
| 03:48 |
Re: inetd(8): continue or exit on error? |
(0) |
David Holland |
| 00:41 |
Re: mtree(8) vs mtree(5) |
(0) |
Joerg Sonnenberger |
| Sat, 03 Jun 2023 |
| 21:40 |
Re: style, sysexits(3), and man RETURN VALUES for |
(0) |
Mouse |
| 21:20 |
Re: mtree(8) vs mtree(5) |
(1) |
Luke Mewburn |
| 18:15 |
Re: style, sysexits(3), and man RETURN VALUES for |
(0) |
tlaronde |
| 16:30 |
Re: style, sysexits(3), and man RETURN VALUES for |
(2) |
Robert Elz |
| 13:53 |
Re: style, sysexits(3), and man RETURN VALUES for |
(1) |
Taylor R Campbell |
| 13:53 |
Re: style, sysexits(3), and man RETURN VALUES for |
(0) |
tlaronde |
| 12:12 |
Re: style, sysexits(3), and man RETURN VALUES for |
(1) |
tlaronde |
| 12:03 |
Re: style, sysexits(3), and man RETURN VALUES for |
(0) |
tlaronde |
| 12:02 |
Re: style, sysexits(3), and man RETURN VALUES for |
(2) |
Taylor R Campbell |
| 12:01 |
Re: style, sysexits(3), and man RETURN VALUES for |
(1) |
Martin Husemann |
| 11:46 |
style, sysexits(3), and man RETURN VALUES for sys |
(3) |
tlaronde |
| 06:41 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| Fri, 02 Jun 2023 |
| 20:59 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Rhialto |
| 11:33 |
Re: [RFC] inetd(8) changes proposal |
(0) |
tlaronde |
| 11:21 |
Re: inetd(8): continue or exit on error? |
(1) |
tlaronde |
| 10:13 |
Re: bl*cklist configuration, ssh only |
(0) |
Michael van Elst |
| 09:43 |
Re: bl*cklist configuration, ssh only |
(1) |
Patrick Welche |
| 07:01 |
Re: inetd(8): continue or exit on error? |
(1) |
David Holland |
| Thu, 01 Jun 2023 |
| 22:06 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Brett Lymn |
| 17:22 |
Re: bl*cklist configuration, ssh only |
(1) |
Michael van Elst |
| 16:06 |
Re: bl*cklist configuration, ssh only |
(1) |
Patrick Welche |
| 12:44 |
mtree(8) vs mtree(5) |
(1) |
Valery Ushakov |
| 07:09 |
Re: [RFC] inetd(8) changes proposal |
(1) |
tlaronde |
| 03:20 |
Re: [RFC] inetd(8) changes proposal |
(1) |
Brett Lymn |