From: 황병희 <soyeomul@doraji.xyz>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44566@debbugs.gnu.org, asjo@koldfront.dk
Subject: bug#44566: 27.1; time bug at Gnus
Date: Wed, 11 Nov 2020 23:18:07 +0900 [thread overview]
Message-ID: <yw9gd1vmr4x.fsf@vtylj.birch.chromebook> (raw)
In-Reply-To: <87o8k4vwbh.fsf@tullinup.koldfront.dk> (unknown@unknown.invalid's message of "Wed, 11 Nov 2020 14:48:18 +0100")
Unknown <unknown@unknown.invalid> writes:
> I have changed the nntp-server in question to always output dates in GMT
> - so instead of:
>
> Date: Wed, 11 Nov 2020 03:18:55 CET
>
> for the article in question, it now outputs:
>
> Date: Wed, 11 Nov 2020 02:18:55 GMT
>
> which should be correct according to rfc2822, I think, and allow Gnus to
> show the correct lapsed time.
Just now i did check that "lapsed time" with GMT (Adam's NNTP
server). Now all is good^^^ Thank you Adam^^^
Sincerely, Gnus fan Byung-Hee
--
^고맙습니다 _和合團結_ 감사합니다_^))//
next prev parent reply other threads:[~2020-11-11 14:18 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 ` 황병희 [this message]
2020-11-11 11:42 ` Peder O. Klingenberg
2020-11-11 11:51 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw9gd1vmr4x.fsf@vtylj.birch.chromebook \
--to=soyeomul@doraji.xyz \
--cc=44566@debbugs.gnu.org \
--cc=asjo@koldfront.dk \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.