From: Jeff Garzik <jgarzik@bitpay.com>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <Bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Fri, 4 Apr 2014 09:19:33 -0400 [thread overview]
Message-ID: <CAJHLa0P9SmynBfJ94A1js30j2OsC0PeEhEy-n+6Wa2Sogo+TNw@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBr-UOqYFGVpann-yUkmB5oj4a7fu=GKw-34+4UMbsP1g@mail.gmail.com>
On Fri, Apr 4, 2014 at 3:01 AM, Wladimir <laanwj@gmail.com> wrote:
> Personally I'd prefer to standardize on ISO 8601 (YYYY-MM-DD) dates as well.
+1 for all-numeric, easily computer parse-able without a lookup table,
and naturally sorts correctly in a lexicographic sort.
English (or any language) should never be in a date format, on a computer.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-04-04 13:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 19:00 [Bitcoin-development] Finite monetary supply for Bitcoin Pieter Wuille
2014-04-01 19:04 ` Matt Whitlock
2014-04-01 20:59 ` Pieter Wuille
2014-04-04 3:41 ` kjj
2014-04-04 7:01 ` Wladimir
2014-04-04 13:19 ` Jeff Garzik [this message]
2014-04-05 10:21 ` Jorge Timón
2014-04-05 10:40 ` Matt Whitlock
2014-04-05 11:28 ` Jorge Timón
2014-04-05 11:28 ` Wladimir
2014-04-05 15:54 ` Daryl Tucker
2014-04-05 17:29 ` Gregory Maxwell
2014-04-01 19:07 ` Gregory Maxwell
2014-04-01 19:09 ` Tamas Blummer
2014-04-01 19:09 ` Mike Hearn
2014-04-01 19:11 ` Matt Corallo
2014-04-01 21:42 ` Jorge Timón
2014-04-01 19:12 ` Luke-Jr
2014-04-01 19:16 ` Benjamin Cordes
2014-04-01 19:19 ` Luke-Jr
2014-04-01 20:00 ` Peter Todd
2014-04-01 20:53 ` Pieter Wuille
2014-04-01 21:47 ` Gregory Maxwell
2014-04-01 21:51 ` Daryl Banttari
2014-04-01 22:03 ` Jeff Garzik
2014-04-01 21:51 ` Matt Corallo
2014-04-01 22:37 ` Pieter Wuille
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=CAJHLa0P9SmynBfJ94A1js30j2OsC0PeEhEy-n+6Wa2Sogo+TNw@mail.gmail.com \
--to=jgarzik@bitpay.com \
--cc=Bitcoin-development@lists.sourceforge.net \
--cc=laanwj@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