From: Andreas Schwab <schwab@linux-m68k.org>
To: "Peder O. Klingenberg" <peder@news.klingenberg.no>
Cc: 44566@debbugs.gnu.org
Subject: bug#44566: 27.1; time bug at Gnus
Date: Wed, 11 Nov 2020 12:51:07 +0100 [thread overview]
Message-ID: <87r1p0jems.fsf@igel.home> (raw)
In-Reply-To: <87tutwqfuu.fsf@news.klingenberg.no> (Peder O. Klingenberg's message of "Wed, 11 Nov 2020 12:42:49 +0100")
On Nov 11 2020, Peder O. Klingenberg wrote:
> Second, the NNTP edition of the same message, with a date header like
> this:
>
> Date: Wed, 11 Nov 2020 03:18:55 CET (8 hours, 22 minutes, 37 seconds ago)
>
> The second timestamp is transposed to CET, but describes the same point
> in time as the first.
No, it describes the date 2020-11-11 03:18:55 +0000. It lacks a time
zone, thus UTC0 is assumed.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-11-11 11:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 2:55 bug#44566: 27.1; time bug at Gnus 황병희
2020-11-11 3:12 ` 황병희
2020-11-11 7:13 ` 황병희
2020-11-11 9:54 ` Unknown
2020-11-11 10:35 ` 황병희
2020-11-11 9:56 ` Lars Ingebrigtsen
2020-11-11 10:39 ` 황병희
2020-11-11 11:14 ` Lars Ingebrigtsen
2020-11-11 11:41 ` 황병희
2020-11-11 11:45 ` Lars Ingebrigtsen
2020-11-11 11:59 ` 황병희
2020-11-11 12:03 ` Lars Ingebrigtsen
2020-11-11 12:12 ` Lars Ingebrigtsen
2020-11-11 12:19 ` 황병희
2020-11-11 12:47 ` Andreas Schwab
2020-11-12 12:45 ` Lars Ingebrigtsen
2020-11-11 13:07 ` Unknown
2020-11-11 13:28 ` Unknown
2020-11-11 13:48 ` Unknown
2020-11-11 14:18 ` 황병희
2020-11-11 11:42 ` Peder O. Klingenberg
2020-11-11 11:51 ` Andreas Schwab [this message]
2020-11-11 13:25 ` Peder O. Klingenberg
2020-11-12 12:11 ` Lars Ingebrigtsen
2020-11-11 11:57 ` Lars Ingebrigtsen
2020-11-11 12:22 ` 황병희
2020-12-12 13:20 ` Lars Ingebrigtsen
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=87r1p0jems.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=44566@debbugs.gnu.org \
--cc=peder@news.klingenberg.no \
/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).