Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WW42Q-0005ap-99 for Bitcoin-development@lists.sourceforge.net; Fri, 04 Apr 2014 13:20:06 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.213.54 as permitted sender) client-ip=209.85.213.54; envelope-from=jgarzik@bitpay.com; helo=mail-yh0-f54.google.com; Received: from mail-yh0-f54.google.com ([209.85.213.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WW42O-0001BX-EL for Bitcoin-development@lists.sourceforge.net; Fri, 04 Apr 2014 13:20:06 +0000 Received: by mail-yh0-f54.google.com with SMTP id f73so3100304yha.27 for ; Fri, 04 Apr 2014 06:19:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=0UQ7Fn8d0CAfUcrs06oeqYsoVdWLLQ+hhZo3J+BCiJc=; b=LJkza1BDCOPFN7hBrbc5rF1qxDfXuIxMG5nGbWYKeEpo8G4FClAiuBFF80ZWhPF7g3 JXqZ2+Z36KsHcd378xL1UlpzdkJ6rES72YVFKJpoDOcqUjl/J7Fib4mTZdCTP1Sq0KWO sJOJ3Ex5eif91F3jsmmkvLPc2xd6a5oo/4sb2lMbs8TIIyZCl2ItJ2rGtp2xR0VTm08N w1rczzH/F+7VLYIWehBkFvXQIaYUHaRQD0ls57ZfNu9xmAtbq7ORJ2dqBzNIhRU695jf gNlc3EBRno0C/NvNIt0MGZ04kUv1ArbPLcS++EiczZD8BsPqPe5IF0votrA534Xjuzo/ YEVg== X-Gm-Message-State: ALoCoQnfPk2YrQFk8t3mRXDbrPXYKJvoUZAJl479fuUNIbhP6qIUuaWa6UHj4pm3VS34kpbnaf6d X-Received: by 10.236.156.65 with SMTP id l41mr17041018yhk.9.1396617593575; Fri, 04 Apr 2014 06:19:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.162.214 with HTTP; Fri, 4 Apr 2014 06:19:33 -0700 (PDT) In-Reply-To: References: <1784069.HYVIiriube@crushinator> <533E29F0.1080901@jerviss.org> From: Jeff Garzik Date: Fri, 4 Apr 2014 09:19:33 -0400 Message-ID: To: Wladimir Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WW42O-0001BX-EL Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2014 13:20:06 -0000 On Fri, Apr 4, 2014 at 3:01 AM, Wladimir 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/