Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.173 as permitted sender)
	client-ip=209.85.213.173; envelope-from=laanwj@gmail.com;
	helo=mail-ig0-f173.google.com; 
MIME-Version: 1.0
In-Reply-To: <533E29F0.1080901@jerviss.org>
References: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>
	<1784069.HYVIiriube@crushinator> <533E29F0.1080901@jerviss.org>
Date: Fri, 4 Apr 2014 09:01:48 +0200
Message-ID: <CA+s+GJBr-UOqYFGVpann-yUkmB5oj4a7fu=GKw-34+4UMbsP1g@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: kjj <bitcoin-devel@jerviss.org>
Content-Type: multipart/alternative; boundary=089e015384fe71514504f632174a
Cc: Bitcoin Dev <Bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Precedence: list

--089e015384fe71514504f632174a
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 4, 2014 at 5:41 AM, kjj <bitcoin-devel@jerviss.org> wrote:

> 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
>

BIPs were based on Python PIPs, PIPs use this same ordering but spell out
the month like '1-Oct-2000'. This is slightly more readable than our format.

http://legacy.python.org/dev/peps/pep-0453/

But to make it more confusing they have two different date conventions
within the header (one for the modified date, and one for the created date).

Personally I'd prefer to standardize on ISO 8601 (YYYY-MM-DD) dates as well.

Feel free to submit a pull against bips/bips that changes around the dates.

Wladimir

--089e015384fe71514504f632174a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Apr 4, 2014 at 5:41 AM, kjj <span dir=3D"ltr">&lt;<a href=3D"mailto:bit=
coin-devel@jerviss.org" target=3D"_blank">bitcoin-devel@jerviss.org</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"">Matt Whit=
lock wrote:<br>
&gt; The creation date in your BIP header has the wrong format. It should b=
e 01-04-2014, per BIP 1.<br>
&gt;<br>
</div>At first, I thought this was a second April Fool&#39;s joke, but then=
 I<br>
looked and saw that all of the BIPs really do use this format. =C2=A0As far=
<br>
as I can tell, we are using this insane format because RFC 822 predates<br>
ISO 8601 by half a decade.<br>
<br>
Since we don&#39;t have half a gajillion mail servers to patch, we could, i=
f<br>
we desired, adopt a sensible date format here. =C2=A0The cost to the<br>
community would be minimal, with probably not more than a half dozen<br>
people needing to update scripts. =C2=A0It could even be as simple as one g=
uy<br>
running sed s/parseabomination/parsedate/g<br></blockquote><div><br></div>B=
IPs were based on Python PIPs, PIPs use this same ordering but spell out th=
e month like &#39;1-Oct-2000&#39;. This is slightly more readable than our =
format.<br>
<div><br><a href=3D"http://legacy.python.org/dev/peps/pep-0453/">http://leg=
acy.python.org/dev/peps/pep-0453/</a><br><br></div><div>But to make it more=
 confusing they have two different date conventions within the header (one =
for the modified date, and one for the created date).<br>
</div><div><br><div>Personally I&#39;d prefer to standardize on ISO 8601 (Y=
YYY-MM-DD) dates as well.<br><br></div><div>Feel free to submit a pull agai=
nst bips/bips that changes around the dates.<br></div><br>Wladimir<br></div=
>
</div><br></div></div>

--089e015384fe71514504f632174a--