Searched hist:1.2032 (Results 1 - 3 of 3) sorted by relevance
| /src/doc/ | ||
| H A D | 3RDPARTY | 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd 1.2032 Sun Aug 18 20:52:03 GMT 2024 christos new ntpd |
| H A D | CHANGES | 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc 1.2032 Sun Jan 04 01:52:24 GMT 2015 christos new yacc |
| /src/distrib/sets/lists/comp/ | ||
| H A D | mi | 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. 1.2032 Sun Apr 24 19:48:30 GMT 2016 dholland Define SEM_VALUE_MAX in only one place. Adding a whole extra header file just for this is not the optimal solution... but stuffing it in with anything else exposes things that otherwise wouldn't be. Nothing in userland should use <sys/semaphore.h> directly, and if some foolish third-party software should decide to do so anyway in spite of the instructions to the contrary I will ruthlessly break it later when the big kernel includes cleanup finally happens. Reported by Kamil Rytarowski, and, as it turns out, also by Klaus Heinz in 2008. |
Completed in 7701 milliseconds