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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1VoZ7I-0007YI-9y
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 13:37:20 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.51 as permitted sender)
client-ip=209.85.214.51; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f51.google.com;
Received: from mail-bk0-f51.google.com ([209.85.214.51])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VoZ7E-0006wo-Ob
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 13:37:20 +0000
Received: by mail-bk0-f51.google.com with SMTP id 6so7122901bkj.38
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Dec 2013 05:37:10 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.204.71.5 with SMTP id f5mr26494307bkj.25.1386250630239; Thu,
05 Dec 2013 05:37:10 -0800 (PST)
Received: by 10.204.69.197 with HTTP; Thu, 5 Dec 2013 05:37:10 -0800 (PST)
Date: Thu, 5 Dec 2013 14:37:10 +0100
Message-ID: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Pieter Wuille <sipa@ulyssis.org>, Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bae499a62c15d04ecc9a010
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: github.com]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VoZ7E-0006wo-Ob
Subject: [Bitcoin-development] Move authorative source for BIPs to git
repository
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: Thu, 05 Dec 2013 13:37:20 -0000
--047d7bae499a62c15d04ecc9a010
Content-Type: text/plain; charset=UTF-8
Hello all,
A while ago after discussion on the mailing list a repository was set up to
store the BIP documents, as this is deemed a more secure solution than
having them on the wiki:
https://github.com/bitcoin/bips
To prevent confusion the next step should probably be to replace the BIPs
on the wiki with links to the github documents, with a notice that changes
should be proposed on github or mailed to the BIP editor (gmaxwell).
Agreed?
Regards,
Wladimir
--047d7bae499a62c15d04ecc9a010
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hello all,<div><br></div><div>A while ago after discussion=
on the mailing list a repository was set up to store the BIP documents, as=
this is deemed a more secure solution than having them on the wiki:</div>
<div><br></div><div><a href=3D"https://github.com/bitcoin/bips">https://git=
hub.com/bitcoin/bips</a><br></div><div><br></div><div>To prevent confusion =
the next step should probably be to replace the BIPs on the wiki with links=
to the github documents, with a notice that changes should be proposed on =
github or mailed to the BIP editor (gmaxwell).</div>
<div><br></div><div>Agreed?</div><div><br></div><div>Regards,<br></div><div=
>Wladimir</div><div><br></div></div>
--047d7bae499a62c15d04ecc9a010--
|