From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range? Date: Mon, 13 Jun 2022 11:25:45 +0200 Message-ID: References: <8735gaqm6i.fsf@localhost> <83wndmutg7.fsf@gnu.org> <87tu8qp5um.fsf@localhost> <83r13uurom.fsf@gnu.org> <83k09mueoc.fsf@gnu.org> <877d5le76w.fsf@yahoo.com> <83bkuxuw4z.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2747"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , Stefan Monnier , Ihor Radchenko , Emacs developers To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jun 13 11:29:11 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o0gNi-0000RD-Cl for ged-emacs-devel@m.gmane-mx.org; Mon, 13 Jun 2022 11:29:10 +0200 Original-Received: from localhost ([::1]:35768 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0gNh-0007Dn-07 for ged-emacs-devel@m.gmane-mx.org; Mon, 13 Jun 2022 05:29:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41990) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0gKo-0004QL-Ia for emacs-devel@gnu.org; Mon, 13 Jun 2022 05:26:10 -0400 Original-Received: from mail-pg1-f180.google.com ([209.85.215.180]:46647) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o0gKl-0006pv-Bx; Mon, 13 Jun 2022 05:26:10 -0400 Original-Received: by mail-pg1-f180.google.com with SMTP id l4so3964462pgh.13; Mon, 13 Jun 2022 02:25:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5JUZgC3sNgA4bCwj1MU9a/6CmlG8Gd698ygH7KhLoII=; b=fP2w1l7/FBZSq87dB/WzMIlOR6UtVRVzFf/dI1VgxVw1j8pC/K7EE/1l35k1LBoS/t 4s4izW/8XPLwFVeJ9Kyox5XDDDYPj69kj8entf07LA/mt0Ds33kduFqLuys6dYzEnVqR dsqrferUB17ERgTFeMbaGh+9N00DPAitLisls4yTyaOVjDnswYeDyZCsqE7f7q4Iy28Q xMmoqn2P8dPHvrJU3FyTXRmt5kfX+nisVpbVSMdauE4ln6URUjKDtoiXSqhECYJU10Ib iaj6/s3RNESgg/ViTxv5I2hrk5H/mnIKD+blxpHtC++8yQ04rw9usiD+EecPI4Lac7XG l6qw== X-Gm-Message-State: AOAM5326mKLwD/BYYqiDlCSl3LH//qgF0KNCUKz/zWcXhlvyuZrRSr8D NjmX/Ljqc5r2l0KRsK0Crzygdu53EIr7FqEysud7UIc6 X-Google-Smtp-Source: ABdhPJyYLiUgWCa+FDKTHyhRGIAUbf52d4P2dPczCt2hWbZHRmLOdpexr20uxUnkfFaF5ZpsQNKma4JaC3jTFPEQWgI= X-Received: by 2002:a63:4447:0:b0:3fc:d3d1:cea9 with SMTP id t7-20020a634447000000b003fcd3d1cea9mr49342666pgk.269.1655112356787; Mon, 13 Jun 2022 02:25:56 -0700 (PDT) In-Reply-To: <83bkuxuw4z.fsf@gnu.org> Received-SPF: pass client-ip=209.85.215.180; envelope-from=stefankangas@gmail.com; helo=mail-pg1-f180.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291133 Archived-At: Eli Zaretskii 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.)