summaryrefslogtreecommitdiff
path: root/c3/b4746bab213575d3db1ceeed327aae05b45905
blob: 2a4f5abf1e0000c27babaf781862ddf95f967ef0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <daryl@daryltucker.com>) id 1WWTED-0002Ji-0y
	for bitcoin-development@lists.sourceforge.net;
	Sat, 05 Apr 2014 16:13:57 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of
	daryltucker.com designates 166.78.160.77 as permitted sender)
	client-ip=166.78.160.77; envelope-from=daryl@daryltucker.com;
	helo=neoretro.net; 
Received: from neoretro.net ([166.78.160.77])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1WWTEB-0002Op-Pj
	for bitcoin-development@lists.sourceforge.net;
	Sat, 05 Apr 2014 16:13:56 +0000
Received: from [10.1.3.104] (ip72-213-200-160.pn.at.cox.net [72.213.200.160])
	(using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by neoretro.net (Postfix) with ESMTPSA id CAB6B1C38F
	for <bitcoin-development@lists.sourceforge.net>;
	Sat,  5 Apr 2014 15:54:30 +0000 (UTC)
Message-ID: <53402724.5060304@daryltucker.com>
Date: Sat, 05 Apr 2014 10:54:12 -0500
From: Daryl Tucker <daryl@daryltucker.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
CC: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
References: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>	<CAJHLa0P9SmynBfJ94A1js30j2OsC0PeEhEy-n+6Wa2Sogo+TNw@mail.gmail.com>	<CAC1+kJPUxNn0iSz=c3OTCFS26sg2jxS-goUdE7LSKphtE9owKw@mail.gmail.com>	<1750679.2ZqEPETxMv@crushinator>
	<CA+s+GJBm_0AX3MTWFvbNw1_GxXFTf_7wHv0GvkATUtz0v6wpsQ@mail.gmail.com>
In-Reply-To: <CA+s+GJBm_0AX3MTWFvbNw1_GxXFTf_7wHv0GvkATUtz0v6wpsQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="lACBUfwvq2GR7l8KQ33QsOMf9EN6Mocn0"
X-Spam-Score: 0.7 (/)
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
	1.2 MISSING_HEADERS        Missing To: header
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1WWTEB-0002Op-Pj
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: Sat, 05 Apr 2014 16:13:57 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--lACBUfwvq2GR7l8KQ33QsOMf9EN6Mocn0
Content-Type: multipart/alternative;
	boundary="------------000308020507040107050108"

This is a multi-part message in MIME format.
--------------000308020507040107050108
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


YYYY-MM-DD sorts more naturally.


On 04/05/2014 06:28 AM, Wladimir wrote:
>
> On Sat, Apr 5, 2014 at 12:40 PM, Matt Whitlock <bip@mattwhitlock.name
> <mailto:bip@mattwhitlock.name>> wrote:
>
>     On Saturday, 5 April 2014, at 12:21 pm, Jorge Tim=F3n wrote:
>     > I like both DD-MM-YYYY and YYYY-MM-DD. I just dislike MM-DD-YYYY
>     and YYYY-DD-MM.
>
>     Your preferences reflect a cultural bias. The only entirely
>     numeric date format that is unambiguous across all cultures is
>     YYYY-MM-DD. (No culture uses YYYY-DD-MM, or at least the ISO seems
>     to think so.)
>
>
> Let's not waste any time shed-painting this. I'd like to finish this
> discussion at once:
>
> https://xkcd.com/1179/
>
> Wladimir
>
>
>
>
> -----------------------------------------------------------------------=
-------
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

--=20
Daryl Tucker
daryl@daryltucker.com


--------------000308020507040107050108
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    YYYY-MM-DD sorts more naturally.<br>
    <br>
    <br>
    <div class=3D"moz-cite-prefix">On 04/05/2014 06:28 AM, Wladimir wrote=
:<br>
    </div>
    <blockquote
cite=3D"mid:CA+s+GJBm_0AX3MTWFvbNw1_GxXFTf_7wHv0GvkATUtz0v6wpsQ@mail.gmai=
l.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Sat, Apr 5, 2014 at 12:40 PM, Mat=
t
            Whitlock <span dir=3D"ltr">&lt;<a moz-do-not-send=3D"true"
                href=3D"mailto:bip@mattwhitlock.name" target=3D"_blank">b=
ip@mattwhitlock.name</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"">On Saturday, 5 April 2014, at 12:21 pm,
                Jorge Tim&oacute;n wrote:<br>
                &gt; I like both DD-MM-YYYY and YYYY-MM-DD. I just
                dislike MM-DD-YYYY and YYYY-DD-MM.<br>
                <br>
              </div>
              Your preferences reflect a cultural bias. The only
              entirely numeric date format that is unambiguous across
              all cultures is YYYY-MM-DD. (No culture uses YYYY-DD-MM,
              or at least the ISO seems to think so.)<br>
            </blockquote>
            <div><br>
              Let's not waste any time shed-painting this. I'd like to
              finish this discussion at once:<br>
              <br>
              <a moz-do-not-send=3D"true" href=3D"https://xkcd.com/1179/"=
>https://xkcd.com/1179/</a><br>
              <br>
            </div>
            <div>Wladimir<br>
            </div>
          </div>
          <br>
          <br>
        </div>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">----------------------------------------------------=
--------------------------
</pre>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
Bitcoin-development mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Bitcoin-development@=
lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/=
lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/l=
istinfo/bitcoin-development</a>
</pre>
    </blockquote>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Daryl Tucker
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:daryl@daryltucker.co=
m">daryl@daryltucker.com</a></pre>
  </body>
</html>

--------------000308020507040107050108--

--lACBUfwvq2GR7l8KQ33QsOMf9EN6Mocn0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTQCckAAoJEEa7mQCz93xzfBgP/jxdbBAuJnJl3IAIQhQ2fn3q
0Wjl83WhBcpI5ZY2HaUDNYhCMG3Mh9SuvT0W9Rm//NXCHT0KMhr8jlS8nGx/HtMV
ztkaiCbwyJSdvSmY+4qG/+ULMpumY512ue3mjBuqb97m6bLfbtkorpMwH3eS4Hf4
OwzzAdUons0mkZCENs+N3MJtK/peZiKl6tMqP+R2GvYuh+L5ev50oQ26pvJrSZLB
qxOhxDwOV7EGfwGgZ4rNnjU6JcHqlrNRyXN+eZd0grJxu/B7q6XNIs4NyZmY6fuu
FrhPXM597GDcO0w2PMcdm7TWPw/0+1rJMgB5D/+sjnM6K6ZhwAlbaV2pWXYBVd+L
Z3WN2kRpQLyMLyK8gXD9Sfq7NMa7YVyxqdmfM+x37S0pG4RksZzHwH/r7Tp7Jtw/
q0FdRbq3ZQpo5I2S67i8JmY1sPffE2YKeLrcUkBYp4Yl7zl8EwTpSzdjOB2rxP9F
3LTOksIC+1rXQmoBBf9KeedUTbx9bf8siiKsNQWNpg1YWAyf96KXRIzPzbx9XrHx
llkY3XlxvWagbGe5NuEEBnuP8/sARHVEAqFTPvGKYf2jepkc+vLnkvWg2KiOjJVm
jYleornPr6+hZbNempNjilpJshStlVbEy4pi1muG/fyUWqPQlsdBvFOOLsYQ7Y0J
O15bYEJgF6LpzwXDksgC
=jqcL
-----END PGP SIGNATURE-----

--lACBUfwvq2GR7l8KQ33QsOMf9EN6Mocn0--