From: "Andrew Pinski" <pinskia@gmail.com>
To: overseers@sourceware.org
Subject: local time seems wrong
Date: Tue, 01 May 2007 22:37:00 -0000 [thread overview]
Message-ID: <de8d50360705011537h66f01f43pac6a8bd5efe6568b@mail.gmail.com> (raw)
I accidently came accross this while looking at the gcc-bugs archives
<http://gcc.gnu.org/ml/gcc-bugs/2007-05/>. The cron job which rotated
the monthly archives looks like it ran an hour early as the archives
contain some entries for March 30th.
I asked this on #gcc today and Joseph Myers mentioned the following:
gcc.gnu.org's /etc/localtime does seem to be a copy of
/usr/share/zoneinfo/Europe/London for some reason. It was meant to be
UTC.
UTC was what I requested in
http://sources.redhat.com/ml/overseers/2003-q1/msg00076.html and I
think that was what was in use until recently.
The timestamp on /etc/localtime is Oct 29 2006.
Seems like we need to change it back to UTC, otherwise we will get
more of these archive problems.
Thanks,
Andrew Pinski
next reply other threads:[~2007-05-01 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 22:37 Andrew Pinski [this message]
2007-05-01 23:10 ` Frank Ch. Eigler
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=de8d50360705011537h66f01f43pac6a8bd5efe6568b@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=overseers@sourceware.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.
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).