Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    TUXPOWER    |    Advocacy for the Linux operating system    |    1,237 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,160 of 1,237    |
|    Maurice Kinal to August Abolins    |
|    shiney new binkd    |
|    14 Jan 26 17:45:35    |
      REPLY: 2:221/1.58@fidonet 286d3cf1       MSGID: 2:280/464.113 6967d63f       CHRS: UTF-8 4       Hej August!              > that means you are building that source using 2017 C standard gcc       > support not the 2023 C standard based gcc default....              Exactly.              > That may mean that gcc developers are getting sloppy,              No it doesn't. Without overthinking this, it means that the binkd source       isn't quite up to speed as far as c standards are concerned and that gcc       provides backwards compatibilty via the -std switch.              > there is an inherent code issue that they are tripping over.              No. It compiles fine by using older c standards without having to revert to       an older gcc release. If anything it is the binkd maintainer(s) who are       behind the times. On the plus side it is a very easy fix and as luck would       have it gnu17 can produce a vastly more capable strftime than gnu99,       especially with regards to rfc-3339 formatted output such as below;               |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca