Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal)

From	"Andrew M.A. Cater" <amacater@einval.com>
Newsgroups	linux.debian.devel
Subject	Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal)
Date	2023-06-01 00:20 +0200
Message-ID	<GBCkF-cMze-1@gated-at.bofh.it> (permalink)
References	<Gx8XU-a0uT-7@gated-at.bofh.it> <GBgtQ-cyCZ-9@gated-at.bofh.it> <GBryV-cFZn-1@gated-at.bofh.it> <GBByi-cM4v-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, May 31, 2023 at 11:24:15PM +0200, Diederik de Haas wrote:
> On Wed May 31, 2023 at 12:44 PM CEST, Wouter Verhelst wrote:
> > On Wed, May 31, 2023 at 12:51:06AM +0200, Diederik de Haas wrote:
> My point is: what about people who don't have the option to *buy*
> anything (new or used), for financial, logistical or other reasons?
> 
> I've been keeping an eye on developments in the upstream linux kernel
> and saw there was a 'spring cleaning' (i.e. removal of old HW support).
> Reading through the commit messages, I noticed 2 criteria for removal:
> - Code has (effectively) been unmaintained for MANY years
> - The maintainers have not seen any indication for several years that
>   ANYONE is actually using that hardware.
> 
> I think those are very reasonable criteria.
> In my initial reply I quoted someone who EXPLICITLY said there were
> people who actually used those i386 devices.
> 
> On the kernel team I've an actual valid argument why supporting i386
> hardware is *difficult* as they don't have the HW (themselves) to
> reproduce an i386-specific issue or to test a potential fix for that.
> 
> In the responses here, I've mostly seen the *assumption* that those old
> devices must be power hungry. While I'm quite sure modern hardware is
> more power *efficient*, that doesn't mean old hardware is thus power
> hungry. 
> But most of all, I'm flabbergasted/annoyed that someone who made explicit and 
> clear what they need, namely keeping support for i386, a bunch of people feel 
> the need to respond like "Well, actually, you need this (other thing)".
> I find that extremely condescending.
> 
> Maybe it's an option to answer the ACTUAL question?
> (and that answer could be 'no')
> 
> > I don't think "but old hardware is still used" is a very good argument
> > for keeping i386 around.
> 
> I think that's actually an excellent reason.
> 
> I've likely missed prior discussions around this subject, but I haven't
> seen and can't think of the reasons why so many people seem so adament
> to get rid of i386 ASAP.

I think I raised this some months ago and was told that it was too late to
make a decision to stop for bookworm but that this was something that 
should be decided early in a release cycle and not at the end when deciding
which architectures wouldn't actually make the cut for release.

It is already hard to test i386 on i686 hardware: as others have said,
most of the tests would be on >> 10 year old hardware.

It does become a law of diminishing returns: if i386 programs had to 
be pulled for security or unmaintainability reasons in the course of bookworm, 
nobody would be surprised.

> 
> Assuming there are indeed valid reasons to get rid of i386, I think it
> would be a far better plan to announce that **Trixie** will be the last
> release that will support i386.

No: announce it at the start of bookworm release and have the Trixie release
team immediately drop it for Trixie
- that way you have five years of support to transition off it.
Otherwise, you've just added _another_ five years of lessening support to
an architecture that won't have been produced for >15 years.


> That way people who care about i386 have a full development cycle to
> make i386 the best it can be for as long as they can still use that HW.
> Maybe they can also make arrangements with CIP to designate the Trixie
> kernel as a Super Long Term Support kernel release.
> 
> But tackling on the release notes at the very last moment that Bookworm

> will be the last supported release, seems not so 'nice' IMO.
> 

As someone who owned and happily used an Asus eePC several years ago: very
nice, silent - it also had a flash disk from the earliest days of flash disks.
If the person who has them still has them all running in another five years,
he will have got an excpetional lifespan out of them. There comes a time
when ports and architectures have to die through lack of hardware or 
maintenance: we've seen that for alpha, varieties of mips and sparc, 
effectively, and the maintainers behind the Debian bsd ports have just
suggested that it should end.

The same arguments that I would now apply to the i386 port I'd also 
apply to early AMD64 hardware - whoever had my first machine with it,
it should now be long gone as power inefficient beyond words and 
15 years old.
> Cheers,
>   Diederik

With best wishes, as ever,

Andy Cater

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