From: Wladimir <laanwj@gmail•com>
To: kjj <bitcoin-devel@jerviss•org>
Cc: Bitcoin Dev <Bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Fri, 4 Apr 2014 09:01:48 +0200 [thread overview]
Message-ID: <CA+s+GJBr-UOqYFGVpann-yUkmB5oj4a7fu=GKw-34+4UMbsP1g@mail.gmail.com> (raw)
In-Reply-To: <533E29F0.1080901@jerviss.org>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1861 bytes --]
next prev parent reply other threads:[~2014-04-04 7:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 19:00 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 [this message]
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
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='CA+s+GJBr-UOqYFGVpann-yUkmB5oj4a7fu=GKw-34+4UMbsP1g@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-devel@jerviss$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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