From: Eli Zaretskii <eliz@gnu.org>
To: Maxim Nikulin <m.a.nikulin@gmail.com>
Cc: larsi@gnus.org, eggert@cs.ucla.edu, 55635-done@debbugs.gnu.org
Subject: bug#55635: `make-decoded-time' incorrectly sets DST to nil, it should be -1 (guess)
Date: Sat, 28 May 2022 19:53:47 +0300 [thread overview]
Message-ID: <83o7zhlht0.fsf@gnu.org> (raw)
In-Reply-To: <0e506652-fb7d-5707-8247-7747ff1e53b0@gmail.com> (message from Maxim Nikulin on Sat, 28 May 2022 23:31:43 +0700)
> Cc: 55635-done@debbugs.gnu.org
> From: Maxim Nikulin <m.a.nikulin@gmail.com>
> Date: Sat, 28 May 2022 23:31:43 +0700
>
> I think, it is confusing that `make-decoded-time' is used to create
> timestamps *and* time intervals. They are different types, for example
> sum of intervals is meaningful (despite may be ambiguous) while there is
> no point to add timestamps.
But this situation already exists with time units anyway. You can add
an hour to some other time, but there's also a valid time stamp that
expresses 1 hour past the epoch UTC, and their values are exactly
identical.
next prev parent reply other threads:[~2022-05-28 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 14:46 bug#55635: `make-decoded-time' incorrectly sets DST to nil, it should be -1 (guess) Maxim Nikulin
2022-05-26 12:13 ` Lars Ingebrigtsen
2022-05-27 2:11 ` Paul Eggert
2022-05-27 10:40 ` Lars Ingebrigtsen
2022-05-27 19:26 ` Paul Eggert
2022-05-28 10:41 ` Lars Ingebrigtsen
2022-05-28 16:31 ` Maxim Nikulin
2022-05-28 16:53 ` Eli Zaretskii [this message]
2022-05-28 17:25 ` Paul Eggert
2022-05-29 13:10 ` Lars Ingebrigtsen
2022-05-29 22:04 ` Paul Eggert
2022-05-31 12:25 ` Maxim Nikulin
2022-06-13 21:30 ` Paul Eggert
2022-06-14 15:57 ` Maxim Nikulin
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=83o7zhlht0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55635-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=m.a.nikulin@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).