blob: f0a0c57ab9a5a3e00fb0c9d00ce0ecd98c770c5e (
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Z6Qw5-0001TL-O9
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Jun 2015 22:08:25 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.173 as permitted sender)
client-ip=209.85.220.173; envelope-from=tier.nolan@gmail.com;
helo=mail-qk0-f173.google.com;
Received: from mail-qk0-f173.google.com ([209.85.220.173])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z6Qw5-0001TV-3y
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Jun 2015 22:08:25 +0000
Received: by qkhu186 with SMTP id u186so80193634qkh.0
for <bitcoin-development@lists.sourceforge.net>;
Sat, 20 Jun 2015 15:08:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.31.85 with SMTP id f82mr35928775qkf.88.1434838099736;
Sat, 20 Jun 2015 15:08:19 -0700 (PDT)
Received: by 10.140.85.241 with HTTP; Sat, 20 Jun 2015 15:08:19 -0700 (PDT)
In-Reply-To: <CABm2gDqPBPiDG1BUAipEsLfyE1VFyvdqdoxtYjkKvGDvBQ8qMg@mail.gmail.com>
References: <CABm2gDqPBPiDG1BUAipEsLfyE1VFyvdqdoxtYjkKvGDvBQ8qMg@mail.gmail.com>
Date: Sat, 20 Jun 2015 23:08:19 +0100
Message-ID: <CAE-z3OVM8vwjo_-FOggSoOWR78w=Rmm+GS7Xv9uSK0jdx1_zdw@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a1147b3ae3ebc740518fa4787
X-Spam-Score: 0.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
(tier.nolan[at]gmail.com)
-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
-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: 1Z6Qw5-0001TV-3y
Subject: Re: [Bitcoin-development] [BIP draft] Motivation and deployment of
consensus rules changes ([soft/hard]forks)
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, 20 Jun 2015 22:08:25 -0000
--001a1147b3ae3ebc740518fa4787
Content-Type: text/plain; charset=UTF-8
The off by 1 bug could be fixed by a soft fork. Since the point is to show
how a non-controversial hard fork works, it doesn't matter much.
--001a1147b3ae3ebc740518fa4787
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">The off by 1 bug could be fixed by a soft fork.=C2=A0 Sinc=
e the point is to show how a non-controversial hard fork works, it doesn=
9;t matter much.<br></div>
--001a1147b3ae3ebc740518fa4787--
|
