Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range?

[Eli Zaretskii <eliz@gnu.org>]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Po Lu <luangruo@yahoo.com>,  yantar92@gmail.com,  emacs-devel@gnu.org
> Date: Mon, 13 Jun 2022 09:19:48 -0400
> 
> Eli Zaretskii [2022-06-13 05:37:00] wrote:
> >> Come 2037, the systems with unfixed libc's will automatically become
> >> obsolete.  We won't have to do anything.
> > Emacs compiled with those obsolete libc versions can be moved to a
> > newer system, and will generally still continue working.
> 
> I don't think so, unless they come with two different `libc`s, in which
> case those applications using the newer `libc` might still work and
> those with the old `libc` won't, but even so users of such a system will
> presumably know that those programs using the old `libc` need to be run
> in a specialized environment with a bogus time or something like that.

You evidently think about systems where libc is a single shared
library, and the _only_ library used by Emacs where the 32-bit time_t
type is used.  Think more generally: what if some of what you consider
'libc' was linked statically into Emacs, and what if some of the other
libraries Emacs uses use 32-bit time type?

> The argument is that whatever happens to Emacs will also happen to ll
> other programs using that same `libc`

That is not necessarily so.