From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ
Date: Fri, 11 Jun 2021 09:38:48 -0400 [thread overview]
Message-ID: <691346aa-38bc-fe9c-bd05-c64add3a9e2c@cornell.edu> (raw)
In-Reply-To: <87r1h9vu3s.fsf@Otto.invalid>
On 6/11/2021 1:38 AM, ASSI wrote:
> Ken Brown via Cygwin writes:
>> Can you be more specific? What goes wrong if TZ is not set? I
>> haven't seen any POSIX or Linux documentation that says it should be
>> set, and I've just checked on two different Linux distros that it's
>> not set by default.
>
> The scripts in base-files were introduced in 2012 after an explicit
> request by Corinna:
>
> https://sourceware.org/legacy-ml/cygwin-developers/2012-01/msg00042.html
>
> Whether any or all of this is still relevant needs to be checked before
> we turn around and change the default again.
Thanks, I wasn't aware of the history. Let's wait until Corinna has a chance to
chime in.
Ken
next prev parent reply other threads:[~2021-06-11 13:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 17:37 Keith Thompson
2021-06-09 3:43 ` Brian Inglis
2021-06-09 22:31 ` Keith Thompson
2021-06-10 2:36 ` Brian Inglis
2021-06-10 14:57 ` Ken Brown
2021-06-10 15:25 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-06-10 18:31 ` Brian Inglis
2021-06-10 19:50 ` Ken Brown
2021-06-11 5:38 ` ASSI
2021-06-11 13:38 ` Ken Brown [this message]
2021-06-11 17:33 ` Brian Inglis
2021-06-11 18:05 ` Ken Brown
2021-06-12 16:34 ` Brian Inglis
2021-06-12 22:44 ` Ken Brown
2021-06-11 10:51 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 6:59 Mike Kaganski
2021-06-08 4:34 ` Russell VT
2021-06-08 7:51 ` Mike Kaganski
2021-06-08 11:37 ` L A Walsh
2021-06-08 12:28 ` Mike Kaganski
2021-06-08 13:04 ` L A Walsh
2021-06-08 13:30 ` Mike Kaganski
2021-06-08 13:57 ` L A Walsh
2021-06-08 14:10 ` Mike Kaganski
2021-06-08 14:15 ` L A Walsh
2021-06-08 13:36 ` Mike Kaganski
2021-06-08 20:03 ` Mike Kaganski
2021-06-09 5:50 ` Brian Inglis
2021-06-11 6:01 ` Mike Kaganski
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=691346aa-38bc-fe9c-bd05-c64add3a9e2c@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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.
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).