Time | Subject | # followups | From |
Tue, 29 Mar 2016 |
17:32 |
Re: Next steps for /bin/sh |
(0) |
Edgar Fuß |
Mon, 28 Mar 2016 |
18:04 |
Re: Patch: rfcomm_sppd + openpty |
(0) |
Iain Hibbert |
10:25 |
Re: Patch: rfcomm_sppd + openpty |
(1) |
Timo Buhrmester |
09:53 |
Re: Patch: rfcomm_sppd + openpty |
(1) |
Iain Hibbert |
08:48 |
Patch: rfcomm_sppd + openpty |
(1) |
Timo Buhrmester |
Sun, 27 Mar 2016 |
00:31 |
Re: Proposal for several minor changes to sh |
(0) |
Robert Elz |
Sat, 26 Mar 2016 |
18:17 |
Re: process mystery |
(0) |
Christos Zoulas |
06:57 |
Re: process mystery |
(3) |
Robert Elz |
01:48 |
process mystery |
(1) |
James K. Lowden |
Fri, 25 Mar 2016 |
12:44 |
Re: strerror(0) POSIX compliance |
(0) |
Christos Zoulas |
02:27 |
Re: strerror(0) POSIX compliance |
(1) |
James K. Lowden |
Thu, 24 Mar 2016 |
23:46 |
Re: pidfile_lock(3) |
(0) |
Steffen Nurpmeso |
22:07 |
Re: strerror(0) POSIX compliance |
(0) |
Michael van Elst |
20:00 |
Re: strerror(0) POSIX compliance |
(0) |
Joerg Sonnenberger |
17:10 |
Re: strerror(0) POSIX compliance |
(2) |
Christos Zoulas |
16:59 |
Re: strerror(0) POSIX compliance |
(2) |
James K. Lowden |
16:59 |
Re: pidfile_lock(3) |
(1) |
James K. Lowden |
15:58 |
Re: strerror(0) POSIX compliance |
(0) |
Joerg Sonnenberger |
14:30 |
Re: strerror(0) POSIX compliance |
(1) |
Michael van Elst |
14:27 |
NLM (was: pidfile_lock(3)) |
(0) |
Edgar Fuß |
14:14 |
Re: pidfile_lock(3) |
(1) |
Thor Lancelot Simon |
13:56 |
Re: strerror(0) POSIX compliance |
(2) |
Greg Troxel |
13:25 |
Re: strerror(0) POSIX compliance |
(1) |
Joerg Sonnenberger |
13:15 |
Re: pidfile_lock(3) |
(0) |
Roy Marples |
12:47 |
Re: pidfile_lock(3) |
(1) |
Michael van Elst |
12:14 |
Re: strerror(0) POSIX compliance |
(0) |
Roy Marples |
12:11 |
Re: strerror(0) POSIX compliance |
(1) |
Jonathan A. Kollasch |
11:59 |
Re: strerror(0) POSIX compliance |
(0) |
Kamil Rytarowski |
11:55 |
Re: pidfile_lock(3) |
(2) |
Roy Marples |
11:49 |
strerror(0) POSIX compliance |
(3) |
Kamil Rytarowski |
07:18 |
Re: pidfile_lock(3) |
(1) |
Michael van Elst |
00:07 |
Re: pidfile_lock(3) |
(1) |
Roy Marples |
Wed, 23 Mar 2016 |
23:55 |
Re: pidfile_lock(3) |
(1) |
Brett Lymn |
Tue, 22 Mar 2016 |
20:44 |
Re: inetd improvements [gsoc16] |
(0) |
Jeremy C. Reed |
20:36 |
Re: Proposal for several minor changes to sh |
(0) |
Iain Hibbert |
18:27 |
Re: Request for feedback: inetd improvements [gsoc |
(0) |
Christos Zoulas |
13:14 |
Re: pidfile_lock(3) |
(0) |
Edgar Fuß |
13:13 |
Re: pidfile_lock(3) |
(1) |
Martin Husemann |
13:11 |
Re: pidfile_lock(3) |
(2) |
Joerg Sonnenberger |
04:55 |
Re: inetd improvements [gsoc16] |
(1) |
Morgan ``Indrora'' Gangwere |
01:58 |
Re: pidfile_lock(3) |
(0) |
Rhialto |
Mon, 21 Mar 2016 |
23:11 |
Request for feedback: inetd improvements [gsoc 201 |
(1) |
Morgan ``indrora'' Gangwere |
23:02 |
Re: pidfile_lock(3) |
(1) |
Thor Lancelot Simon |
22:30 |
Re: pidfile_lock(3) |
(0) |
James K. Lowden |
20:32 |
Re: pidfile_lock(3) |
(0) |
Michael van Elst |
19:48 |
Feedback on Draft |
(0) |
Shalom Ray |
17:21 |
Re: pidfile_lock(3) |
(1) |
David Young |
16:44 |
Re: pidfile_lock(3) |
(2) |
Roy Marples |
14:55 |
Re: pidfile_lock(3) |
(2) |
Thor Lancelot Simon |
14:30 |
Re: pidfile_lock(3) |
(1) |
Roy Marples |
00:46 |
Re: pidfile_lock(3) |
(1) |
Thor Lancelot Simon |
00:43 |
Re: pidfile_lock(3) |
(2) |
Thor Lancelot Simon |
Sun, 20 Mar 2016 |
23:19 |
Re: pidfile_lock(3) |
(0) |
Christos Zoulas |
23:13 |
Re: pidfile_lock(3) |
(1) |
Roy Marples |
23:05 |
Re: pidfile_lock(3) |
(1) |
Christos Zoulas |
20:53 |
Re: pidfile_lock(3) |
(1) |
Roy Marples |
19:28 |
Re: Google summer code 2016 project ideas |
(0) |
Christos Zoulas |
19:02 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
18:53 |
Re: pidfile_lock(3) |
(2) |
James K. Lowden |
17:51 |
Re: pidfile_lock(3) |
(0) |
Michael van Elst |
15:40 |
Re: pidfile_lock(3) |
(0) |
Roy Marples |
14:58 |
Patch for bin/50460 |
(0) |
Abhinav Upadhyay |
14:05 |
Re: pidfile_lock(3) |
(2) |
Roy Marples |
13:46 |
Re: pidfile_lock(3) |
(1) |
Roy Marples |
09:26 |
Re: pidfile_lock(3) |
(2) |
Michael van Elst |
Sat, 19 Mar 2016 |
23:29 |
pidfile_lock(3) |
(3) |
Roy Marples |
Fri, 18 Mar 2016 |
20:06 |
Re: shmod |
(0) |
James K. Lowden |
06:51 |
Re: shmod |
(1) |
Jan Danielsson |
03:49 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
00:34 |
shmod |
(1) |
James K. Lowden |
Wed, 16 Mar 2016 |
05:13 |
Proposal for several minor changes to sh |
(2) |
Robert Elz |
Tue, 15 Mar 2016 |
09:21 |
Re: Revised Web UI for NPF as a GSoC project |
(0) |
Mateusz Kocielski |
Mon, 14 Mar 2016 |
22:37 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
21:48 |
Re: Revised Web UI for NPF as a GSoC project |
(1) |
Aleksej Saushev |
20:27 |
Revised Web UI for NPF as a GSoC project |
(1) |
coypu |
11:13 |
Re: Web UI for NPF as a GSoC project |
(0) |
Marc Balmer |
02:09 |
Re: Web UI for NPF as a GSoC project |
(0) |
Christos Zoulas |
Sun, 13 Mar 2016 |
23:58 |
Re: Results of || and && operators in /bin/sh $(( |
(0) |
Robert Elz |
21:56 |
Re: Web UI for NPF as a GSoC project |
(0) |
Aleksej Saushev |
21:29 |
Re: Web UI for NPF as a GSoC project |
(0) |
Travis Paul |
21:24 |
Re: Web UI for NPF as a GSoC project |
(1) |
Kamil Rytarowski |
21:11 |
Re: Web UI for NPF as a GSoC project |
(2) |
Martin Husemann |
21:09 |
Re: Results of || and && operators in /bin/sh $(( |
(0) |
Aleksej Saushev |
21:00 |
Re: Web UI for NPF as a GSoC project |
(1) |
Christos Zoulas |
16:54 |
Re: Web UI for NPF as a GSoC project |
(2) |
coypu |
16:34 |
Re: Web UI for NPF as a GSoC project |
(1) |
Christos Zoulas |
14:09 |
Re: performance of shell read loops |
(0) |
Joerg Sonnenberger |
12:53 |
Re: Results of || and && operators in /bin/sh $(( |
(2) |
Matt Sporleder |
12:36 |
Re: Results of || and && operators in /bin/sh $(( |
(1) |
Aleksej Saushev |
12:35 |
Web UI for NPF as a GSoC project |
(1) |
coypu |
10:50 |
Re: performance of shell read loops |
(0) |
David Laight |
05:31 |
Re: Google summer code 2016 project ideas |
(1) |
Christos Zoulas |
04:28 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
Sat, 12 Mar 2016 |
21:10 |
Results of || and && operators in /bin/sh $(( )) e |
(1) |
Robert Elz |
17:38 |
Re: What should we do with the -n flag in sh ? |
(0) |
Robert Elz |
15:25 |
Re: Next steps for /bin/sh |
(0) |
Robert Elz |
15:18 |
Re: performance of shell read loops |
(2) |
Robert Elz |
13:55 |
Re: performance of shell read loops |
(0) |
Joerg Sonnenberger |
13:54 |
Re: Next steps for /bin/sh |
(0) |
Joerg Sonnenberger |
13:34 |
Re: Next steps for /bin/sh |
(2) |
David Laight |
13:30 |
Re: Next steps for /bin/sh |
(0) |
David Laight |
13:26 |
Re: performance of shell read loops |
(2) |
David Laight |
11:16 |
Re: What should we do with the -n flag in sh ? |
(0) |
David Laight |
Fri, 11 Mar 2016 |
12:06 |
Re: Next steps for /bin/sh |
(0) |
Robert Elz |
05:26 |
Re: Next steps for /bin/sh |
(0) |
Joerg Sonnenberger |
05:24 |
Re: Next steps for /bin/sh |
(1) |
Joerg Sonnenberger |
00:53 |
Next steps for /bin/sh |
(4) |
Robert Elz |
Thu, 10 Mar 2016 |
04:08 |
Re: Google summer code 2016 project ideas |
(0) |
Christos Zoulas |
03:32 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
Wed, 09 Mar 2016 |
22:46 |
Re: Google summer code 2016 project ideas |
(2) |
Charles Cui |
22:42 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
22:35 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
20:21 |
Re: Google summer code 2016 project ideas |
(1) |
Christos Zoulas |
20:20 |
Re: Google summer code 2016 project ideas |
(0) |
Christos Zoulas |
13:54 |
Re: Google summer code 2016 project ideas |
(1) |
Christos Zoulas |
09:20 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
Mon, 07 Mar 2016 |
19:05 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
09:09 |
Re: performance of shell read loops |
(1) |
Robert Elz |
08:52 |
Re: performance of shell read loops |
(0) |
Robert Elz |
05:21 |
performance of shell read loops |
(2) |
David Holland |
01:02 |
Re: Google summer code 2016 project ideas |
(1) |
Christos Zoulas |
Sun, 06 Mar 2016 |
17:21 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
Sat, 05 Mar 2016 |
20:50 |
Re: cp -i might violate POSIX |
(0) |
David Holland |
19:54 |
Re: cp -i might violate POSIX |
(0) |
Valery Ushakov |
02:28 |
Re: cp -i might violate POSIX |
(0) |
Timo Buhrmester |
01:50 |
Re: cp -i might violate POSIX |
(0) |
Timo Buhrmester |
00:41 |
cp -i might violate POSIX |
(2) |
Timo Buhrmester |
Fri, 04 Mar 2016 |
22:02 |
Re: inetd improvements [gsoc16] |
(1) |
Christos Zoulas |
20:17 |
Re: inetd improvements [gsoc16] |
(1) |
Morgan ``indrora'' Gangwere |
Thu, 03 Mar 2016 |
08:42 |
Re: Google summer code 2016 project ideas |
(0) |
Charles Cui |
00:50 |
Re: inetd improvements [gsoc16] |
(0) |
James K. Lowden |
Wed, 02 Mar 2016 |
22:54 |
Re: Google summer code 2016 project ideas |
(1) |
Charles Cui |
15:55 |
Re: Google summer code 2016 project ideas |
(2) |
Christos Zoulas |
15:48 |
Re: inetd improvements [gsoc16] |
(2) |
Christos Zoulas |
06:01 |
Google summer code 2016 project ideas |
(1) |
Charles Cui |
Tue, 01 Mar 2016 |
23:55 |
Re: Next steps for /bin/sh |
(0) |
James K. Lowden |
22:24 |
inetd improvements [gsoc16] |
(1) |
Morgan ``indrora'' Gangwere |
12:59 |
Re: Next steps for /bin/sh |
(2) |
Robert Elz |
12:49 |
Re: Google summer code 2016 project ideas |
(0) |
Christos Zoulas |
11:42 |
Google summer code 2016 project ideas |
(1) |
Charles Cui |
10:50 |
Re: removing an envsys temperature limit |
(0) |
Constantine A. Murenin |