blob: 2ff2afae09ad77d171476bd7d15f6958dd1d6a72 (
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1VoZuC-0000fo-W1
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 14:27:53 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([192.3.11.21])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1VoZuB-0003X5-Ud for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 14:27:52 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id E7E0710803C0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 5 Dec 2013 14:27:57 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Thu, 5 Dec 2013 14:27:43 +0000
User-Agent: KMail/1.13.7 (Linux/3.12.1-gentoo; KDE/4.10.5; x86_64; ; )
References: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
In-Reply-To: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201312051427.44179.luke@dashjr.org>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
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]
X-Headers-End: 1VoZuB-0003X5-Ud
Subject: Re: [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 14:27:53 -0000
On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
> 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?
I think this would stifle active BIP draft editing. We're already having a
hard time getting some developers to write BIPs for their proposals - I don't
think we should be putting up bigger hurdles.
Luke
|
