Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.devel > #108162
| From | Thorsten Glaser <tg@debian.org> |
|---|---|
| Newsgroups | linux.debian.devel |
| Subject | Re: 64-bit time_t transition for 32-bit archs: a proposal |
| Date | 2023-06-09 19:00 +0200 |
| Message-ID | <GENCV-eLRb-1@gated-at.bofh.it> (permalink) |
| References | <GwgNP-9s1z-1@gated-at.bofh.it> <GDzsl-e0D6-3@gated-at.bofh.it> <GDKQN-e7rS-3@gated-at.bofh.it> <GErsJ-ey7C-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Helmut Grohne dixit: >I'm inclined to call this consensus now and therefore ask those that do >not agree with it to reply here - even if your reply is only stating I disagree. I would like to see a long-term commitment against electronic waste and to see support for i386 as a second-class but fully supported platform, with 64-bit time_t and off_t, d-i, kernel and everything. In particular I would, at the same time, like the baseline lowered to i586 again. It was raised mostly for multimedia stuff, and it’s now justifyable to ask people to use amd64 or armhf or something for that. Besides being a fully supported bootable platform for old but still serviceable hardware the M-A support is also worthwhile. I run the i386 version of firefox-esr on some systems to naturally limit its resource usage, for example. Ideally we’d keep the old i386 around for legacy binary-only libraries and executables and add an i586 architecture with a differing dynamic linker path; all solibs would be in the M-A-qualified path anyway. Maybe we could even use one of the various existing ELF header fields to distinguish them for the kernel, if needed. I’m mildly willing to help out as part of a porter team, but not be the only porter. I do have an affected system (EeePC, though I need to do some hardware maintenance (HDD swap etc.) first) which I occasionally use. That being said I’ve reduced my involvement in bookworm/sid due to the systemdification, so I would prefer to not be the primarily respon‐ sible developer. bye, //mirabilos - -- „Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu installieren.“ -- XTaran auf der OpenRheinRuhr, ganz begeistert (EN: “[…]uhr.gz is a reason to install mksh on every system.”) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (MirBSD) Comment: ☃ ЦΤℱ—8 ☕☂☄ iQIcBAEBCQAGBQJkg1XOAAoJEHa1NLLpkAfgTvYP/ie/yyFeDYQTGJjKdjYoFThr ckaL1VYC2C1pBQLFbcdeRG2Zy2VyQQzJQnFxfBey4PKJAvvY78VyI/1Kn4eGXWKE 7KNPB11tm5IZaQa/fIUpWDTruzkFydkuYAjT72qiHqkBphF32YbiNSLeQEf8pEfJ bbk2Z1awKM5wm6dw0iXEn+IV2YDXzPt2Mb0HgLu08b2MjyFI6pou6UjLmriqeKd6 qpiTH1XzKGkOrRh00LRGEg4GuRpjboaxtaJoTykEj+42xxyy21yzrxigrpxc7fpl 7gkCfpBvf8XFORHsZuLA/ZoepKpII4BIP8qgwip3D8sy9kyJRlFpN87KGJhMiTMz 2cPtXHtwYkMMRjMcOJazaGXm3QgzOKF1cNBaQFer/N74X9P8k5ax4e9B6plrsDdX eI62d8U2D9IUSHE3S+OWRIqXhb/2RJ+DcCca182344PyDKz+j0x3RLwXcAPTGTZS Dxf7LSSZ4nOFUAW31ZNbeByjM40RXlzGbQu63Bps1Vwzy3N+xMNfj0fd3XEx+rDd edDYXHe2gt5lQJuG6n6REs/DdoBD1724IOIAm0j4IF4UDPuhpILN9RSmvSECDDnP +aPQ+P8YkKOP3NeVnE/Jd7pbqvt0vvYjXUhuXEMf2I2UT2KG1j0tonv/5G8W4ui0 +ZX+kIdFDYBmx2opmp/Z =lfL0 -----END PGP SIGNATURE-----
Back to linux.debian.devel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-17 06:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-17 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal YunQiang Su <wzssyqa@gmail.com> - 2023-05-17 07:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 22:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Florian Lohoff <f@zz.de> - 2023-05-22 10:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 07:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Marco d'Itri <md@Linux.IT> - 2023-05-18 12:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-18 16:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Wookey <wookey@wookware.org> - 2023-05-18 18:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Olaf Titz <olaf@bigred.inka.de> - 2023-06-26 20:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-18 16:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2023-05-18 21:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-18 21:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-05-17 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 07:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-05-28 21:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Craig Small <csmall@debian.org> - 2023-05-17 14:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-17 17:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-05-18 03:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 21:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-05-19 05:40 +0200
i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 13:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Luca Boccassi <bluca@debian.org> - 2023-05-19 14:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 16:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "G. Branden Robinson" <g.branden.robinson@gmail.com> - 2023-05-19 16:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Colin Watson <cjwatson@debian.org> - 2023-05-19 16:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "G. Branden Robinson" <g.branden.robinson@gmail.com> - 2023-05-19 17:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 19:40 +0200
Re: i386 in the future Ivan Shmakov <ivan@siamics.net> - 2023-05-25 13:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Simon McVittie <smcv@debian.org> - 2023-05-19 17:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-19 18:00 +0200
partial support for i386 (Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal)) Michael Biebl <biebl@debian.org> - 2023-05-19 19:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Jonathan Carter <jcc@debian.org> - 2023-05-22 12:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-05-19 17:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-19 18:00 +0200
Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386 Ansgar <ansgar@43-1.org> - 2023-05-19 17:40 +0200
Re: Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386 Michael Biebl <biebl@debian.org> - 2023-05-19 19:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "Andrew M.A. Cater" <amacater@einval.com> - 2023-05-19 19:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Cyril Brulebois <kibi@debian.org> - 2023-05-19 19:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Michael Biebl <biebl@debian.org> - 2023-05-19 20:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 19:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Bjørn Mork <bjorn@mork.no> - 2023-05-19 21:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Ansgar <ansgar@43-1.org> - 2023-05-19 22:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Bjørn Mork <bjorn@mork.no> - 2023-05-19 22:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Cyril Brulebois <kibi@debian.org> - 2023-05-20 07:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-20 14:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Diederik de Haas <didi.debian@cknow.org> - 2023-05-31 01:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-31 06:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) John Goerzen <jgoerzen@complete.org> - 2023-05-31 14:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Sven Hoexter <sven@stormbind.net> - 2023-05-31 16:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Gunnar Wolf <gwolf@debian.org> - 2023-05-31 18:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Wookey <wookey@wookware.org> - 2023-05-31 20:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Ansgar <ansgar@43-1.org> - 2023-05-31 21:30 +0200
Re: Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-05-31 07:00 +0200
Re: Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-31 10:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Wouter Verhelst <wouter@debian.org> - 2023-05-31 12:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Alexandre Detiste <alexandre.detiste@gmail.com> - 2023-05-31 13:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Sven Hoexter <sven@stormbind.net> - 2023-05-31 16:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Gunnar Wolf <gwolf@debian.org> - 2023-05-31 18:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Diederik de Haas <didi.debian@cknow.org> - 2023-05-31 23:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "Andrew M.A. Cater" <amacater@einval.com> - 2023-06-01 00:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Adam Borowski <kilobyte@angband.pl> - 2023-06-01 15:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) nick black <dankamongmen@gmail.com> - 2023-06-02 19:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Wouter Verhelst <wouter@debian.org> - 2023-06-02 21:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Diederik de Haas <didi.debian@cknow.org> - 2023-06-02 23:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Paul Wise <pabs@debian.org> - 2023-06-01 03:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "Theodore Ts'o" <tytso@mit.edu> - 2023-06-01 14:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com> - 2023-06-08 02:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-19 17:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 19:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Guillem Jover <guillem@debian.org> - 2023-05-19 20:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-19 20:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Ansgar <ansgar@43-1.org> - 2023-05-20 00:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-21 08:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Roger Lynn <Roger@rilynn.me.uk> - 2023-05-26 01:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-26 06:50 +0200
Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Josh Triplett <josh@joshtriplett.org> - 2023-05-20 09:20 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Simon Richter <sjr@debian.org> - 2023-05-20 11:30 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Adam Borowski <kilobyte@angband.pl> - 2023-05-20 18:50 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Stephen Kitt <skitt@debian.org> - 2023-05-21 20:00 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] James Addison <jay@jp-hosting.net> - 2023-05-22 14:30 +0200
Re: i386 in the future Wookey <wookey@wookware.org> - 2023-05-20 05:30 +0200
Re: i386 in the future Ansgar <ansgar@43-1.org> - 2023-05-20 10:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-23 03:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-06-08 04:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-06-14 06:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-06-17 17:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 08:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-20 02:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Wookey <wookey@wookware.org> - 2023-05-20 13:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Andreas Metzler <ametzler@bebt.de> - 2023-05-20 17:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-23 03:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-23 03:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-06-06 09:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-06 12:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Luca Boccassi <bluca@debian.org> - 2023-06-06 13:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Marco d'Itri <md@Linux.IT> - 2023-06-06 17:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Gunnar Wolf <gwolf@debian.org> - 2023-06-06 20:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-06 21:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Alexis Murzeau <amubtdx@gmail.com> - 2023-06-06 21:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-08 21:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-07 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Andreas Metzler <ametzler@bebt.de> - 2023-06-08 07:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-08 21:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-08 07:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Bastien ROUCARIES <roucaries.bastien@gmail.com> - 2023-06-08 08:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Hakan Bayındır <hakan@bayindir.org> - 2023-06-08 10:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Holger Levsen <holger@layer-acht.org> - 2023-06-08 11:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-09 06:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Holger Levsen <holger@layer-acht.org> - 2023-06-09 11:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Ansgar <ansgar@43-1.org> - 2023-06-09 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Bastian Blank <waldi@debian.org> - 2023-06-08 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-08 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Gunnar Wolf <gwolf@debian.org> - 2023-06-08 17:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal nick black <dankamongmen@gmail.com> - 2023-06-09 01:30 +0200
Re: multiarch vs. multilib Simon McVittie <smcv@debian.org> - 2023-06-09 11:00 +0200
Re: multiarch vs. multilib nick black <dankamongmen@gmail.com> - 2023-06-11 10:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-09 05:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-09 11:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-09 06:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Bastian Blank <waldi@debian.org> - 2023-06-09 08:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Wookey <wookey@wookware.org> - 2023-07-05 18:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-06-06 21:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-07 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-06-08 19:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Holger Levsen <holger@layer-acht.org> - 2023-06-08 20:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-06-08 21:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-06-09 19:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Aurelien Jarno <aurel32@debian.org> - 2023-06-26 21:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal James Addison <jay@jp-hosting.net> - 2023-06-27 10:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-07-06 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-07-06 18:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-07-06 23:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-07-07 01:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Sam Hartman <hartmans@debian.org> - 2023-07-06 22:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-07 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Sune Vuorela <nospam@vuorela.dk> - 2023-06-07 09:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal "Peter Van Eynde" <pvaneynd@debian.org> - 2023-06-07 10:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-07 12:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal The Wanderer <wanderer@fastmail.fm> - 2023-06-07 13:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-07-06 19:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-07-06 19:20 +0200
[i386] adlibtracker2 and fp-units-i386 Ivan Shmakov <ivan@siamics.net> - 2023-06-07 15:40 +0200
Constructive contributions (was: Re: 64-bit time_t transition for 32-bit archs: a proposal) Jonathan Carter <jcc@debian.org> - 2023-06-09 13:30 +0200
csiph-web