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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <andyparkins@gmail.com>) id 1QrVs8-00087k-Sl
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Aug 2011 14:04:32 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=andyparkins@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QrVs8-0005Re-6S
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Aug 2011 14:04:32 +0000
Received: by wwf25 with SMTP id 25so1862984wwf.10
for <bitcoin-development@lists.sourceforge.net>;
Thu, 11 Aug 2011 07:04:26 -0700 (PDT)
Received: by 10.216.61.136 with SMTP id w8mr317414wec.75.1313071466039;
Thu, 11 Aug 2011 07:04:26 -0700 (PDT)
Received: from dvr.localnet (mail.360visiontechnology.com [92.42.121.178])
by mx.google.com with ESMTPS id a43sm1260925wed.4.2011.08.11.07.04.24
(version=TLSv1/SSLv3 cipher=OTHER);
Thu, 11 Aug 2011 07:04:25 -0700 (PDT)
From: Andy Parkins <andyparkins@gmail.com>
To: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com>
Date: Thu, 11 Aug 2011 15:04:22 +0100
User-Agent: KMail/1.13.6 (Linux/2.6.38-2-686; KDE/4.6.3; i686; ; )
References: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com>
<201108110647.35194.andyparkins@gmail.com>
<1313063130.18196.154.camel@mei>
In-Reply-To: <1313063130.18196.154.camel@mei>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart7822937.8DvMklt1uh";
protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201108111504.22851.andyparkins@gmail.com>
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
(andyparkins[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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QrVs8-0005Re-6S
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Change to multiple executables?
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, 11 Aug 2011 14:04:33 -0000
--nextPart7822937.8DvMklt1uh
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
On 2011 August 11 Thursday, Joel Joonatan Kaartinen wrote:
> On Thu, 2011-08-11 at 06:47 +0100, Andy Parkins wrote:
> > Again you're missing my point... you are still shooting ideas down.
>=20
> And you're only shooting his actions down without indicating clearly
Yeah, shooting down a shooting down, which you've just shot down. Where wi=
ll=20
it end?
> what you think ought to be done instead. What do you want him to say
> instead?
How about:
"This is a good idea, but we don't want to break backward compatibility a=20
little piece at a time. Instead we'd like to collect all such changes into=
=20
one single compatibility breaking release. Here's the wiki page you should=
=20
update; and here's the git branch you should push changes like this to."
> most suggestions you point at have been discussed about before
I know the application/protocol version split has been discussed before, bu=
t=20
please point me to the relevant discussion on: loading the block chain in=20
reverse; transaction only requests; checksumming removal; verack removal;=20
storing script parameters outside the script; and requesting blocks by=20
transaction hash instead of block hash.
If I've missed all of these discussions and their inevitable logically=20
indisputable rejection, I apologise.
Andy
=2D-=20
Dr Andy Parkins
andyparkins@gmail.com
--nextPart7822937.8DvMklt1uh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEABECAAYFAk5D4WYACgkQwQJ9gE9xL215mwCgorfkV3/KYzJx0Kv7/YOsaVsy
xmoAoM7hVIiJ8bvszt3J5NUUEloYWAJg
=KN2H
-----END PGP SIGNATURE-----
--nextPart7822937.8DvMklt1uh--
|
