diff options
| author | kjj <bitcoin-devel@jerviss.org> | 2014-04-03 22:41:36 -0500 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-04 03:41:46 +0000 |
| commit | 431719d09a275c98ff3f0dbe6ef53db729389d41 (patch) | |
| tree | 65e131b6996c5ee0fe6bedfe315cd6ef44c9706d | |
| parent | 174fa2ffc9d8c25b5a2cbb88f0665d3d6b2fe80a (diff) | |
| download | pi-bitcoindev-431719d09a275c98ff3f0dbe6ef53db729389d41.tar.gz pi-bitcoindev-431719d09a275c98ff3f0dbe6ef53db729389d41.zip | |
Re: [Bitcoin-development] Finite monetary supply for Bitcoin
| -rw-r--r-- | ff/6e1f9e32926354b4fa13bbca6ca48d1615d392 | 70 |
1 files changed, 70 insertions, 0 deletions
diff --git a/ff/6e1f9e32926354b4fa13bbca6ca48d1615d392 b/ff/6e1f9e32926354b4fa13bbca6ca48d1615d392 new file mode 100644 index 000000000..b98bef861 --- /dev/null +++ b/ff/6e1f9e32926354b4fa13bbca6ca48d1615d392 @@ -0,0 +1,70 @@ +Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from + <SRS0=hyUuVC/F=ZE=jerviss.org=bitcoin-devel@jerviss.org>) + id 1WVv0k-0001Au-Fw for Bitcoin-development@lists.sourceforge.net; + Fri, 04 Apr 2014 03:41:46 +0000 +X-ACL-Warn: +Received: from serv.jerviss.org ([12.47.47.47] helo=inana.jerviss.org) + by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) + (Exim 4.76) id 1WVv0j-00016q-ON + for Bitcoin-development@lists.sourceforge.net; + Fri, 04 Apr 2014 03:41:46 +0000 +Received: from [10.8.2.254] ([192.151.168.151]) + (username: kjj authenticated by PLAIN symmetric_key_bits=0) + by inana.jerviss.org (8.13.6/8.12.11) with ESMTP id s343fcAJ019215 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) + for <Bitcoin-development@lists.sourceforge.net>; + Thu, 3 Apr 2014 22:41:39 -0500 +Message-ID: <533E29F0.1080901@jerviss.org> +Date: Thu, 03 Apr 2014 22:41:36 -0500 +From: kjj <bitcoin-devel@jerviss.org> +User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; + rv:28.0) Gecko/20100101 SeaMonkey/2.25 +MIME-Version: 1.0 +To: Bitcoin-development@lists.sourceforge.net +References: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com> + <1784069.HYVIiriube@crushinator> +In-Reply-To: <1784069.HYVIiriube@crushinator> +Content-Type: text/plain; charset=ISO-8859-1; format=flowed +Content-Transfer-Encoding: 7bit +Received-SPF: pass (inana.jerviss.org: 192.151.168.151 is authenticated by a + trusted mechanism) +X-Spam-Score: -2.1 (--) +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.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain +X-Headers-End: 1WVv0j-00016q-ON +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: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Fri, 04 Apr 2014 03:41:46 -0000 + +Matt Whitlock wrote: +> The creation date in your BIP header has the wrong format. It should be 01-04-2014, per BIP 1. +> +At first, I thought this was a second April Fool's joke, but then I +looked and saw that all of the BIPs really do use this format. As far +as I can tell, we are using this insane format because RFC 822 predates +ISO 8601 by half a decade. + +Since we don't have half a gajillion mail servers to patch, we could, if +we desired, adopt a sensible date format here. The cost to the +community would be minimal, with probably not more than a half dozen +people needing to update scripts. It could even be as simple as one guy +running sed s/parseabomination/parsedate/g + + |