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 ) 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 ; 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 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: <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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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