public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Btc Drak <btcdrak@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
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
Date: Fri, 18 Sep 2015 21:34:59 +0100	[thread overview]
Message-ID: <CADJgMzvcR8O1pQDFVAp2Ndu-a7-VoCtckcPSogQvMUqa6a55bA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgR59+iFjg5n6des50rJCA8vkRAvjKC3QgRjiYSyy-bA9A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

Urgh... Can we hardfork time? It's clearly in need of an upgrade...

On Fri, Sep 18, 2015 at 9:31 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:

> 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.
>

[-- Attachment #2: Type: text/html, Size: 1233 bytes --]

  reply	other threads:[~2015-09-18 20:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  1:07 [bitcoin-dev] Weekly development meetings on IRC Wladimir J. van der Laan
2015-09-18  2:56 ` Alex Morcos
2015-09-18  4:19   ` Peter Todd
2015-09-18  4:30 ` Mark Friedenbach
2015-09-18  4:57 ` Luke Dashjr
2015-09-18  7:04   ` Jonas Schnelli
2015-09-18  8:20     ` Eric Lombrozo
2015-09-18 20:14 ` Matt Corallo
2015-09-18 20:24   ` Btc Drak
2015-09-18 20:27     ` Matt Corallo
2015-09-18 20:30       ` Jeffrey Paul
2015-09-18 20:34         ` Matt Corallo
2015-09-18 20:31       ` Gregory Maxwell
2015-09-18 20:34         ` Btc Drak [this message]
2015-09-21 13:01           ` jl2012
2015-09-18 20:36         ` Matt Corallo
2015-09-18 21:50     ` Luke Dashjr
2015-09-18 23:29       ` Dave Scotese
2015-09-18 21:50     ` Luke Dashjr
2015-09-21 13:29 ` Wladimir J. van der Laan
2015-09-21 13:51   ` gb
2015-09-22 14:03     ` Wladimir J. van der Laan

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=CADJgMzvcR8O1pQDFVAp2Ndu-a7-VoCtckcPSogQvMUqa6a55bA@mail.gmail.com \
    --to=btcdrak@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=cory@coryfields.com \
    --cc=gmaxwell@gmail.com \
    --cc=pieter.wuille@gmail.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