unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 19302@debbugs.gnu.org, ivan@siamics.net
Subject: bug#19302: 24.4.51; `date-to-time' fails after 2038
Date: Tue, 09 Dec 2014 21:09:31 +0200	[thread overview]
Message-ID: <831to8wsgk.fsf@gnu.org> (raw)
In-Reply-To: <m3sigozlz1.fsf@stories.gnus.org>

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: 19302@debbugs.gnu.org,  ivan@siamics.net
> Date: Tue, 09 Dec 2014 20:01:22 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> The problem is in parsing dates in the far future.  Web pages, for
> >> instance, popularly use an Expiry: header saying that the page expires
> >> in the year 2100 as a synonym for "never expires".
> >
> > So we are going now to reinvent all the strftime stuff, complete with
> > localized names of months, days, etyc., is that so?
> 
> Not at all.  I'm just explaining what the use case it.

I understood, and even agreed.

> My solution would be to just document this ("Emacs does not support
> dates further into the future than 2038 on OS-es with 32-bit
> time_t") and move on.

Yes.





  reply	other threads:[~2014-12-09 19:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  1:58 bug#19302: 24.4.51; `date-to-time' fails after 2038 Gabriel
2014-12-08  3:59 ` Lars Magne Ingebrigtsen
2014-12-08 12:54   ` Gabriel
2014-12-08 20:59   ` Richard Stallman
2014-12-08 22:02     ` Lars Magne Ingebrigtsen
2014-12-09 11:01       ` Richard Stallman
2014-12-09 16:38         ` Eli Zaretskii
2014-12-09 18:17           ` Ivan Shmakov
2014-12-09 18:26             ` Eli Zaretskii
2014-12-09 18:31               ` Lars Magne Ingebrigtsen
2014-12-09 18:49                 ` Eli Zaretskii
2014-12-09 19:01                   ` Lars Magne Ingebrigtsen
2014-12-09 19:09                     ` Eli Zaretskii [this message]
2014-12-10  0:41                       ` Gabriel
2014-12-10 16:25                         ` Eli Zaretskii
2014-12-11  0:31                           ` bug#19302: [PATCH] " Gabriel
2014-12-11  9:25                             ` Andreas Schwab
2014-12-09 20:52                     ` Andreas Schwab
2014-12-09 19:07                   ` Ivan Shmakov
2014-12-09 19:48                     ` Eli Zaretskii
2014-12-10 16:18                 ` Richard Stallman
2014-12-10 21:21                   ` Gabriel
2014-12-11 19:49                     ` Richard Stallman
2014-12-12  0:33                       ` Gabriel
2014-12-10 16:18           ` Richard Stallman
2014-12-10  0:37         ` Stefan Monnier
2014-12-10 16:17           ` Richard Stallman
2014-12-10 19:59             ` Stefan Monnier
2014-12-11 19:49               ` Richard Stallman
2014-12-11 20:31                 ` Stefan Monnier
2014-12-12 16:42                   ` Richard Stallman
2019-11-02  0:11                   ` Stefan Kangas
2020-02-29 18:17                   ` Stefan Kangas
2020-02-29 20:06                     ` Stefan Monnier
2020-03-01  1:30                       ` Stefan Kangas
2020-03-01  3:56                         ` Stefan Monnier
2020-03-02 10:43                           ` Stefan Kangas
2020-03-09  0:10                           ` Stefan Kangas

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=831to8wsgk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19302@debbugs.gnu.org \
    --cc=ivan@siamics.net \
    --cc=larsi@gnus.org \
    /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).