public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daryl Tucker <daryl@daryltucker.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Sat, 05 Apr 2014 10:54:12 -0500	[thread overview]
Message-ID: <53402724.5060304@daryltucker.com> (raw)
In-Reply-To: <CA+s+GJBm_0AX3MTWFvbNw1_GxXFTf_7wHv0GvkATUtz0v6wpsQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1091 bytes --]


YYYY-MM-DD sorts more naturally.


On 04/05/2014 06:28 AM, Wladimir wrote:
>
> On Sat, Apr 5, 2014 at 12:40 PM, Matt Whitlock <bip@mattwhitlock.name
> <mailto:bip@mattwhitlock.name>> wrote:
>
>     On Saturday, 5 April 2014, at 12:21 pm, Jorge Timón wrote:
>     > I like both DD-MM-YYYY and YYYY-MM-DD. I just dislike MM-DD-YYYY
>     and YYYY-DD-MM.
>
>     Your preferences reflect a cultural bias. The only entirely
>     numeric date format that is unambiguous across all cultures is
>     YYYY-MM-DD. (No culture uses YYYY-DD-MM, or at least the ISO seems
>     to think so.)
>
>
> Let's not waste any time shed-painting this. I'd like to finish this
> discussion at once:
>
> https://xkcd.com/1179/
>
> Wladimir
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

-- 
Daryl Tucker
daryl@daryltucker.com


[-- Attachment #1.2: Type: text/html, Size: 2861 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-04-05 16:13 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
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 [this message]
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=53402724.5060304@daryltucker.com \
    --to=daryl@daryltucker.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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