all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: monnier@iro.umontreal.ca, yantar92@gmail.com, emacs-devel@gnu.org
Subject: Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range?
Date: Mon, 13 Jun 2022 05:37:00 +0300	[thread overview]
Message-ID: <83bkuxuw4z.fsf@gnu.org> (raw)
In-Reply-To: <877d5le76w.fsf@yahoo.com> (message from Po Lu on Mon, 13 Jun 2022 08:30:15 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  yantar92@gmail.com,
>   emacs-devel@gnu.org
> Date: Mon, 13 Jun 2022 08:30:15 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > That's true, but we will have to at least say something about dropping
> > support for libc's that don't.  Or something.
> 
> 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.  So the
system can still be alive, but such an old-compiled Emacs on that
system will die.  We will need at least to mention that somewhere.



  reply	other threads:[~2022-06-13  2:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12  9:13 What were the Emacs versions with dates limited to 1970 .. 2037 year range? Ihor Radchenko
2022-06-12  9:22 ` Eli Zaretskii
2022-06-12  9:51   ` Ihor Radchenko
2022-06-12 10:00     ` Eli Zaretskii
2022-06-12 14:21       ` Stefan Monnier
2022-06-12 14:41         ` Eli Zaretskii
2022-06-13  0:30           ` Po Lu
2022-06-13  2:37             ` Eli Zaretskii [this message]
2022-06-13  9:25               ` Stefan Kangas
2022-06-13 11:49                 ` Eli Zaretskii
2022-06-13 13:19               ` Stefan Monnier
2022-06-13 13:29                 ` Eli Zaretskii
2022-06-13 16:40                   ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bkuxuw4z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=yantar92@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.