MIME-Version: 1.0
In-Reply-To: <55FC7394.4060901@mattcorallo.com>
References: <20150918010709.GB5251@amethyst.visucore.com>
	<55FC70A5.9080603@mattcorallo.com>
	<CADJgMzsuBrXT1qOAScu+fv_A7Du1XrFoix8nSO14qXj2YD4KtQ@mail.gmail.com>
	<55FC7394.4060901@mattcorallo.com>
Date: Fri, 18 Sep 2015 20:31:28 +0000
Message-ID: <CAAS2fgR59+iFjg5n6des50rJCA8vkRAvjKC3QgRjiYSyy-bA9A@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Matt Corallo <lf-lists@mattcorallo.com>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>,
	Cory Fields <cory@coryfields.com>, Pieter Wuille <pieter.wuille@gmail.com>
Subject: Re: [bitcoin-dev] Weekly development meetings on IRC
Precedence: list

On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Google Calendar is localized, but has an option to change the timezone
> of an event, it just doesnt have UTC in its options. So, yes, we should
> use something that observes DST in roughly the same way as everyone else
> - CEST/PDT/EST/etc.

uh. There is fairly little global consistency in DST usage. Lots of
places do dst on different dates.

So if it's in some DST timezone it's likely to move twice each change
for some subset of the people who do it.

E.g. europe and US end DST one week apart.