Groups | Search | Server Info | Login | Register
31122 articles, 921 threads (numbers 1000 – 32532) — flat view
| Advanced| Subject | Author | Date |
|---|---|---|
| good post on LinkedIn (53 replies) | Niocláisín Cóilín de Ghlostéir <Master_Fontaine_is_dishonest@Strand_in_London.Gov.UK> | 2025-02-22 21:12 +0100 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <Spamassassin@irrt.De> | 2025-08-29 16:16 +0200 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-01 18:52 +0100 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-02 01:40 +0000 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-29 14:26 +0000 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-29 09:04 -0800 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-29 17:57 +0000 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-29 10:59 -0800 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-30 00:48 +0000 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-29 17:01 -0800 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-30 01:28 +0000 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-01-30 15:14 +1100 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-30 11:52 -0800 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-01-31 16:05 +1100 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 12:34 +0000 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-31 07:29 -0800 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-02-01 20:59 +1100 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-02-01 03:06 -0800 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-02-02 00:17 +1100 |
| → Re: Excel and accountants, good post on LinkedIn | John Levine <johnl@taugh.com> | 2026-01-31 23:21 +0000 |
| → Re: Excel and accountants, good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-31 16:22 -0800 |
| → Re: Excel and accountants, good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-02-01 02:13 +0000 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 03:56 +0000 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-01-31 15:23 +1100 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 14:36 +0000 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-02-01 21:31 +1100 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-01-30 14:59 +1100 |
| → Re: good post on LinkedIn | liz@poppyrecords.invalid.invalid (Liz Tuddenham) | 2026-01-30 10:15 +0000 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-01-31 00:06 +1100 |
| → Re: good post on LinkedIn | Gerhard Hoffmann <dk4xp@arcor.de> | 2026-01-30 15:06 +0100 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-30 11:55 -0800 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 13:33 +0000 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-02-01 01:31 +1100 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 19:16 +0000 |
| → Re: history of Fortran, good post on LinkedIn | John Levine <johnl@taugh.com> | 2026-01-31 23:10 +0000 |
| → Sorry re history of Fortran, good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 23:25 +0000 |
| → Re: Sorry re history of Fortran, good post on LinkedIn | John Levine <johnl@taugh.com> | 2026-02-01 02:43 +0000 |
| → Re: Sorry re history of Fortran, good post on LinkedIn | OrangeFish <OrangeFish@invalid.invalid> | 2026-02-01 18:00 -0500 |
| → Re: Sorry re history of Fortran, good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-02-18 14:56 +0000 |
| → Re: Sorry re history of Fortran, good post on LinkedIn | John Levine <johnl@taugh.com> | 2026-02-18 20:32 +0000 |
| → Re: Sorry re history of Fortran, good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-02-18 23:20 +0000 |
| → Re: old new postings Sorry re history of Fortran, good post on LinkedIn | John Levine <johnl@taugh.com> | 2026-02-19 02:46 +0000 |
| → Re: old new postings Sorry re history of Fortran, good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-02-19 11:33 +0000 |
| → Re: Sorry re history of Fortran, good post on LinkedIn | George Neuner <gneuner2@comcast.net> | 2026-02-19 22:28 -0500 |
| → Re: history of Fortran, good post on LinkedIn | albert@spenarnc.xs4all.nl | 2026-02-01 22:11 +0100 |
| → Re: good post on LinkedIn | Bill Sloman <bill.sloman@ieee.org> | 2026-02-01 21:36 +1100 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 14:26 +0000 |
| → Re: good post on LinkedIn | wmartin <wwm@wwmartin.net> | 2026-01-30 11:27 -0800 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-30 18:54 -0800 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 03:40 +0000 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 15:20 +0000 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-01-31 17:13 +0000 |
| → Re: good post on LinkedIn | john larkin <jl@glen--canyon.com> | 2026-01-31 07:55 -0800 |
| → Re: good post on LinkedIn | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2026-02-16 13:52 +0000 |
| Ada-Europe Conference - Extended Deadlines - AEiC 2026 | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2026-02-12 22:28 +0000 |
| Return of the Overlays! (11 replies) | Don Y <blockedofcourse@foo.invalid> | 2026-01-13 17:03 -0700 |
| → Re: Return of the Overlays! | George Neuner <gneuner2@comcast.net> | 2026-01-14 01:11 -0500 |
| → Re: Return of the Overlays! | Don Y <blockedofcourse@foo.invalid> | 2026-01-14 13:39 -0700 |
| → Re: Return of the Overlays! | George Neuner <gneuner2@comcast.net> | 2026-01-15 03:06 -0500 |
| → Re: Return of the Overlays! | Don Y <blockedofcourse@foo.invalid> | 2026-01-15 03:25 -0700 |
| → Re: Return of the Overlays! | George Neuner <gneuner2@comcast.net> | 2026-01-17 01:23 -0500 |
| → Re: Return of the Overlays! | John Levine <johnl@taugh.com> | 2026-01-14 20:39 +0000 |
| → Re: Return of the Overlays! | Grant Edwards <invalid@invalid.invalid> | 2026-01-14 21:00 +0000 |
| → Re: Return of the Overlays! | Don Y <blockedofcourse@foo.invalid> | 2026-01-14 18:55 -0700 |
| → Re: Return of the Overlays! | Don Y <blockedofcourse@foo.invalid> | 2026-01-14 18:48 -0700 |
| → Re: Return of the Overlays! | Don Y <blockedofcourse@foo.invalid> | 2026-01-25 01:46 -0700 |
| → Re: Return of the Overlays! | Don Y <blockedofcourse@foo.invalid> | 2026-01-25 02:10 -0700 |
| arm-gcc, Cortex-M0+, uint64_t and alignment (18 replies) | pozz <pozzugno@gmail.com> | 2026-01-20 13:26 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-20 17:07 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | Grant Edwards <invalid@invalid.invalid> | 2026-01-20 16:41 +0000 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | pozz <pozzugno@gmail.com> | 2026-01-20 18:09 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-20 18:44 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | pozz <pozzugno@gmail.com> | 2026-01-21 09:11 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-21 10:02 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | pozz <pozzugno@gmail.com> | 2026-01-21 15:58 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-21 17:13 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | pozz <pozzugno@gmail.com> | 2026-01-21 17:57 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-22 10:03 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | Grant Edwards <invalid@invalid.invalid> | 2026-01-20 17:48 +0000 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-20 18:41 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | Grant Edwards <invalid@invalid.invalid> | 2026-01-20 18:10 +0000 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-20 22:32 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | Grant Edwards <invalid@invalid.invalid> | 2026-01-21 03:38 +0000 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-21 08:54 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | pozz <pozzugno@gmail.com> | 2026-01-20 17:55 +0100 |
| → Re: arm-gcc, Cortex-M0+, uint64_t and alignment | David Brown <david.brown@hesbynett.no> | 2026-01-20 22:24 +0100 |
| Ada-Europe Conference - 13 Feb Journal Track Extended Deadline | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2026-01-08 21:23 +0000 |
| Christmas circuits | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> | 2025-12-25 00:50 +0100 |
| Ada-Europe Conference - 2nd Call for Contributions - AEiC 2026 | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2025-11-20 15:31 +0000 |
| CfC 30th Ada-Europe Int. Conf. Reliable Software Technologies | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2025-09-24 15:50 +0000 |
| A TclOO debug question (1 reply) | Helmut Giese <hgiese@ratiosoft.com> | 2025-07-31 22:15 +0200 |
| → Re: A TclOO debug question | Helmut Giese <hgiese@ratiosoft.com> | 2025-07-31 22:16 +0200 |
| Improving build system (20 replies) | pozz <pozzugno@gmail.com> | 2025-05-13 17:57 +0200 |
| → Re: Improving build system | Nicolas Paul Colin de Glocester <Spamassassin@irrt.De> | 2025-05-13 22:48 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-14 11:03 +0200 |
| → Re: Improving build system | George Neuner <gneuner2@comcast.net> | 2025-05-14 15:21 -0400 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-15 09:48 +0200 |
| → Re: Improving build system | Nioclás Pól Caileán de Ghloucester <Spamassassin@irrt.De> | 2025-07-04 18:38 +0200 |
| → Re: Improving build system | pozz <pozzugno@gmail.com> | 2025-05-14 23:51 +0200 |
| → Re: Improving build system | Nicolas Paul Colin de Glocester <Spamassassin@irrt.De> | 2025-05-15 01:00 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-15 11:17 +0200 |
| → Re: Improving build system | Nicolas Paul Colin de Glocester <Spamassassin@irrt.De> | 2025-05-16 12:21 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-16 14:42 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-15 11:03 +0200 |
| → Re: Improving build system | pozz <pozzugno@gmail.com> | 2025-05-15 23:25 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-16 11:12 +0200 |
| → Re: Improving build system | pozz <pozzugno@gmail.com> | 2025-05-16 12:46 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-16 15:30 +0200 |
| → Re: Improving build system | pozz <pozzugno@gmail.com> | 2025-05-16 16:17 +0200 |
| → Re: Improving build system | pozz <pozzugno@gmail.com> | 2025-05-16 15:45 +0200 |
| → Re: Improving build system | David Brown <david.brown@hesbynett.no> | 2025-05-16 17:20 +0200 |
| → Re: Improving build system | pozz <pozzugno@gmail.com> | 2025-05-17 10:56 +0200 |
| → Re: Improving build system | Stefan Reuther <stefan.news@arcor.de> | 2025-05-14 18:06 +0200 |
| NVIDIA Spark Process (1 reply) | Niocláisín Cóilín de Ghlostéir <Spamassassin@irrt.De> | 2025-06-10 00:47 +0200 |
| → Re: NVIDIA Spark Process | john larkin <jl@glen--canyon.com> | 2025-06-09 16:02 -0700 |
| CERN FPGA meeting | Niocláisín Cóilín de Ghlostéir <Spamassassin@irrt.De> | 2025-05-28 11:47 +0200 |
| Ada-Europe - AEiC 2025 early registration deadline imminent | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2025-05-24 21:16 +0000 |
| Ada-Europe Int.Conf. Reliable Software Technologies, AEiC 2025 | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2025-05-12 20:12 +0000 |
| Do you use Upwork? (2 replies) | Nicolas Paul Colin de Glocester <Spamassassin@irrt.De> | 2025-05-11 14:30 +0200 |
| → Re: Do you use Upwork? | Nicolas Paul Colin de Glocester <Spamassassin@irrt.De> | 2025-05-12 17:18 +0200 |
| → Re: Do you use Upwork? | Nicolas Paul Colin de Glocester <Spamassassin@irrt.De> | 2025-05-12 18:44 +0200 |
| Voice compression (6 replies) | pozz <pozzugno@gmail.com> | 2025-04-02 18:33 +0200 |
| → Re: Voice compression | Rafael Deliano <Rafael_Deliano@arcor.de> | 2025-04-02 19:55 +0200 |
| → Re: Voice compression | pozz <pozzugno@gmail.com> | 2025-04-03 19:53 +0200 |
| → Re: Voice compression | Rafael Deliano <Rafael_Deliano@arcor.de> | 2025-04-05 11:12 +0200 |
| → Re: Voice compression | pozz <pozzugno@gmail.com> | 2025-04-07 13:13 +0200 |
| → Re: Voice compression | Paul Rubin <no.email@nospam.invalid> | 2025-04-04 13:54 -0700 |
| → Re: Voice compression | pozz <pozzugno@gmail.com> | 2025-04-07 13:09 +0200 |
| gcc arm inline asm: how to output value for .set directive? (2 replies) | Grant Edwards <invalid@invalid.invalid> | 2025-04-03 22:04 +0000 |
| → Re: gcc arm inline asm: how to output value for .set directive? | Grant Edwards <invalid@invalid.invalid> | 2025-04-03 23:06 +0000 |
| → Re: gcc arm inline asm: how to output value for .set directive? | David Brown <david.brown@hesbynett.no> | 2025-04-04 11:25 +0200 |
| 32 bits time_t and Y2038 issue (54 replies) | pozz <pozzugno@gmail.com> | 2025-03-11 16:22 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-11 17:32 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-11 23:21 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-12 10:33 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-12 16:48 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-12 17:39 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-12 18:13 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-12 19:18 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-13 09:57 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-13 16:51 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-14 13:27 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-14 14:20 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-12 08:44 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-12 11:14 +0100 |
| → Re: 32 bits time_t and Y2038 issue | antispam@fricas.org (Waldek Hebisch) | 2025-03-14 01:48 +0000 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-14 08:36 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-15 16:30 +0000 |
| → Re: 32 bits time_t and Y2038 issue | Grant Edwards <invalid@invalid.invalid> | 2025-03-15 17:02 +0000 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-15 23:26 +0000 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-18 09:21 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-18 11:34 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-18 17:31 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-18 20:29 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-21 09:20 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-21 13:54 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-21 20:53 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-22 11:19 +0100 |
| → Re: 32 bits time_t and Y2038 issue | antispam@fricas.org (Waldek Hebisch) | 2025-03-21 14:35 +0000 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-18 18:28 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-18 20:43 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Grant Edwards <invalid@invalid.invalid> | 2025-03-18 20:58 +0000 |
| → Re: 32 bits time_t and Y2038 issue | Hans-Bernhard Bröker <HBBroeker@gmail.com> | 2025-03-18 23:31 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-19 11:24 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Grant Edwards <invalid@invalid.invalid> | 2025-03-19 14:27 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-19 17:33 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Grant Edwards <invalid@invalid.invalid> | 2025-03-19 19:08 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-19 21:14 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-21 09:48 +0000 |
| → Re: 32 bits time_t and Y2038 issue | Grant Edwards <invalid@invalid.invalid> | 2025-03-21 13:27 +0000 |
| → Re: 32 bits time_t and Y2038 issue | antispam@fricas.org (Waldek Hebisch) | 2025-03-19 22:09 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-20 09:26 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-21 22:40 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-21 09:23 +0000 |
| → Re: 32 bits time_t and Y2038 issue | Hans-Bernhard Bröker <HBBroeker@gmail.com> | 2025-03-21 22:38 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-19 08:24 +0100 |
| → Re: 32 bits time_t and Y2038 issue | antispam@fricas.org (Waldek Hebisch) | 2025-03-21 14:04 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-21 16:45 +0100 |
| → Re: 32 bits time_t and Y2038 issue | pozz <pozzugno@gmail.com> | 2025-03-21 22:51 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Hans-Bernhard Bröker <HBBroeker@gmail.com> | 2025-03-22 00:00 +0100 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-22 14:29 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-22 14:46 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-22 17:57 +0100 |
| → Re: 32 bits time_t and Y2038 issue | antispam@fricas.org (Waldek Hebisch) | 2025-03-22 15:57 +0000 |
| → Re: 32 bits time_t and Y2038 issue | David Brown <david.brown@hesbynett.no> | 2025-03-22 18:02 +0100 |
| → Re: 32 bits time_t and Y2038 issue | Michael Schwingen <news-1513678000@discworld.dascon.de> | 2025-03-18 18:44 +0000 |
| AEiC 2025 - Ada-Europe conference - CfC for Additional Tracks | dirk@orka.cs.kuleuven.be. (Dirk Craeynest) | 2025-02-18 19:26 +0000 |
| How to add the second (or other) languages (12 replies) | pozz <pozzugno@gmail.com> | 2025-02-12 17:26 +0100 |
| → Re: How to add the second (or other) languages | Stefan Reuther <stefan.news@arcor.de> | 2025-02-12 18:14 +0100 |
| → Re: How to add the second (or other) languages | David Brown <david.brown@hesbynett.no> | 2025-02-12 20:50 +0100 |
| → Re: How to add the second (or other) languages | pozz <pozzugno@gmail.com> | 2025-02-16 19:59 +0100 |
| → Re: How to add the second (or other) languages | David Brown <david.brown@hesbynett.no> | 2025-02-17 09:51 +0100 |
| → Re: How to add the second (or other) languages | pozz <pozzugno@gmail.com> | 2025-02-17 16:05 +0100 |
| → Re: How to add the second (or other) languages | David Brown <david.brown@hesbynett.no> | 2025-02-17 19:09 +0100 |
| → Re: How to add the second (or other) languages | pozz <pozzugno@gmail.com> | 2025-02-16 22:56 +0100 |
| → Re: How to add the second (or other) languages | David Brown <david.brown@hesbynett.no> | 2025-02-17 09:57 +0100 |
| → Re: How to add the second (or other) languages | pozz <pozzugno@gmail.com> | 2025-02-16 23:15 +0100 |
| → Re: How to add the second (or other) languages | David Brown <david.brown@hesbynett.no> | 2025-02-17 09:59 +0100 |
| → Re: How to add the second (or other) languages | Stefan Reuther <stefan.news@arcor.de> | 2025-02-17 19:00 +0100 |
| → Re: How to add the second (or other) languages | "Niocláiſín Cóilín de Ġloſtéir" <Master_Fontaine_is_dishonest@Strand_in_London.Gov.UK> | 2025-02-13 22:51 +0100 |
~Page 1 of ~144 (articles 32345–32532) Older →
csiph-web