From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Date/Time?
Date: Sun, 20 May 2018 16:58:58 -0400 [thread overview]
Message-ID: <f9ad1c73-d672-0cfc-4e67-faee2dcbd9df@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1805191129020.10948@i7.lan>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On 05/19/2018 02:45 PM, speck for Linus Torvalds wrote:
>
>
> On Sat, 19 May 2018, speck for Borislav Petkov wrote:
>>
>> Says here: "May 21st 2100 UTC".
>
> What an odd time. It's noon in the Aleutian Islands and absolutely nowhere
> else that I can find.
>
> I guess it's "after trading closes", but that would be 4pm eastern. And
> 2100 UTC is 5pm EDT, so it's _really_ after.
>
> So I wonder why that particular choice.
>
> Whatever. It's 2pm for me. I guess it's 11pm for Greg in Paris.
>
> Are we sure that's not a typo, and it's supposed to be noon UTC,
> transposing the two digits?
It's 2pm PDT because Intel asked GPZ if "21st" could mean "the afternoon
of the 21st" in order to allow various CERT briefings and the like. It
was apparently deemed reasonable by the Google powers that be.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-05-20 21:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 17:26 [MODERATED] Date/Time? Greg KH
2018-05-19 17:51 ` [MODERATED] Date/Time? Borislav Petkov
2018-05-19 18:45 ` Linus Torvalds
2018-05-19 19:07 ` [MODERATED] " Borislav Petkov
2018-05-19 19:48 ` Linus Torvalds
2018-05-19 20:22 ` [MODERATED] " Borislav Petkov
2018-05-20 20:58 ` Jon Masters [this message]
2018-05-19 18:21 ` David Woodhouse
2018-05-19 19:05 ` Greg KH
2018-05-20 19:23 ` David Woodhouse
2018-05-20 23:01 ` David Woodhouse
2018-05-21 8:35 ` Greg KH
2018-05-20 17:45 ` Jiri Kosina
2018-05-20 18:19 ` Greg KH
2018-05-20 18:35 ` Borislav Petkov
2018-05-20 19:57 ` Greg KH
2018-05-20 18:36 ` Linus Torvalds
2018-05-20 18:48 ` Jiri Kosina
2018-05-20 20:59 ` Jon Masters
2018-05-20 21:09 ` Jiri Kosina
2018-05-21 6:11 ` Greg KH
2018-05-20 21:48 ` Linus Torvalds
2018-05-20 21:56 ` David Woodhouse
2018-05-21 6:16 ` Greg KH
2018-05-21 7:18 ` David Woodhouse
2018-05-21 15:23 ` Date/Time? Thomas Gleixner
2018-05-21 16:46 ` [MODERATED] Date/Time? Greg KH
2018-05-21 17:12 ` Konrad Rzeszutek Wilk
2018-05-21 19:42 ` Greg KH
2018-05-21 19:48 ` Jiri Kosina
2018-05-21 20:30 ` Jon Masters
2018-05-22 8:00 ` Peter Zijlstra
2018-05-22 9:26 ` Greg KH
2018-05-22 16:32 ` Andi Kleen
2018-05-23 14:15 ` Jon Masters
2018-05-21 17:22 ` Jon Masters
2018-05-21 18:56 ` Date/Time? Thomas Gleixner
2018-05-21 19:16 ` [MODERATED] Date/Time? Jon Masters
2018-05-21 20:43 ` Greg KH
2018-05-21 17:31 ` Jon Masters
2018-05-21 18:53 ` Date/Time? Thomas Gleixner
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=f9ad1c73-d672-0cfc-4e67-faee2dcbd9df@redhat.com \
--to=jcm@redhat.com \
--cc=speck@linutronix.de \
/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 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.