unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: luangruo@yahoo.com, 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 14:49:04 +0300	[thread overview]
Message-ID: <837d5kvl5b.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=jK3Wu-Wd=+oXo5QF5QA44oHoYD9hPg3wvg+U5UaitfA@mail.gmail.com> (message from Stefan Kangas on Mon, 13 Jun 2022 11:25:45 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Mon, 13 Jun 2022 11:25:45 +0200
> Cc: Po Lu <luangruo@yahoo.com>, Stefan Monnier <monnier@iro.umontreal.ca>, 
> 	Ihor Radchenko <yantar92@gmail.com>, Emacs developers <emacs-devel@gnu.org>
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> Would it be worth writing an entry in the FAQ?  (I'm not volunteering:
> I don't know enough to write it.)

If someone knows what and how to write (I don't), I think this could
be a useful addition to the FAQ.



  reply	other threads:[~2022-06-13 11:49 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
2022-06-13  9:25               ` Stefan Kangas
2022-06-13 11:49                 ` Eli Zaretskii [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=837d5kvl5b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).