blob: 3a894b824a537197d63200e95095c515123055e9 (
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
|
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 <laanwj@gmail.com>) id 1XeeRu-0008Sw-K1
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Oct 2014 06:22:10 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.181 as permitted sender)
client-ip=209.85.223.181; envelope-from=laanwj@gmail.com;
helo=mail-ie0-f181.google.com;
Received: from mail-ie0-f181.google.com ([209.85.223.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XeeRt-0002Ks-UX
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Oct 2014 06:22:10 +0000
Received: by mail-ie0-f181.google.com with SMTP id at20so2774713iec.40
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Oct 2014 23:22:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.37.15 with SMTP id l15mr15223671iol.40.1413440524559;
Wed, 15 Oct 2014 23:22:04 -0700 (PDT)
Received: by 10.64.141.112 with HTTP; Wed, 15 Oct 2014 23:22:04 -0700 (PDT)
In-Reply-To: <201410160436.52259.luke@dashjr.org>
References: <CA+s+GJApfj5OAxGyHG9CsmRHTpAQBgC44iU2U99LwNGNZDATBw@mail.gmail.com>
<201410160436.52259.luke@dashjr.org>
Date: Thu, 16 Oct 2014 08:22:04 +0200
Message-ID: <CA+s+GJAhJTXZwotBzGMh_D3ZadjuP-UtOV+Xv+pBMZ7QOH21GQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1XeeRt-0002Ks-UX
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP status changes
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, 16 Oct 2014 06:22:10 -0000
>
> Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
Not really. BIP changes should be discussed on the mailing list,
that's the way to get community consensus (as specified in BIP1).
Wladimir
|
