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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1RLjli-000418-LS
for bitcoin-development@lists.sourceforge.net;
Wed, 02 Nov 2011 22:58:50 +0000
X-ACL-Warn:
Received: from nm14-vm6.bullet.mail.ne1.yahoo.com ([98.138.91.107])
by sog-mx-4.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1RLjlh-0001bu-DC for bitcoin-development@lists.sourceforge.net;
Wed, 02 Nov 2011 22:58:50 +0000
Received: from [98.138.90.51] by nm14.bullet.mail.ne1.yahoo.com with NNFMP;
02 Nov 2011 22:58:44 -0000
Received: from [98.138.89.199] by tm4.bullet.mail.ne1.yahoo.com with NNFMP;
02 Nov 2011 22:58:44 -0000
Received: from [127.0.0.1] by omp1057.mail.ne1.yahoo.com with NNFMP;
02 Nov 2011 22:58:44 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 29314.58914.bm@omp1057.mail.ne1.yahoo.com
Received: (qmail 44908 invoked by uid 60001); 2 Nov 2011 22:58:43 -0000
X-YMail-OSG: LyumXy0VM1nOdWgwZzLZTxkm6dfRhLYQu1J5PiO.z4cswul
hO39UOGE85ZQpQnDTdLGwOjHCmmEycbAIPoKLk914DesSklU8HBRenjQAmuP
4wTokOnfdpG.QSkaWcw0Bpn9ETnh0ZQs_FWHjzRPdr3VMNvKwS2kHovBUuwH
I.NM2taMcgirFJzxfuLu1brqFmmRTCf6ezJOtdxhCOwhbgk3i9.xC8QOFtqg
tIDhRkFCcdb1BIlBYZ5NbmX3A.KNkZM6NXXRGbWR2uIBUhtHHAg03Hycb5dv
qZ_b68UEzQoxN00Do5TnLhKY7wkSbRXZqrv_Zqv5EcMDGZfwTNYuX9Vkbh5X
yj4ED.dAy3s9Y_FFiw_yaOXzDtbIyelzIcgkX9X_BJ.ydB8i38Mrn5iH66IJ
wrpl9rtvs5Xh9HjT9g_R4trN9H5y3mGdNcwNFOcS9yIhJ8w12VaCNVtK39q2
AzPa4yvKV3mVHdo9wayi5ZqDbLE3Fw8PJyfvw9sy__rTVVY2oP_mTyX1XhtE -
Received: from [92.20.177.18] by web121017.mail.ne1.yahoo.com via HTTP;
Wed, 02 Nov 2011 15:58:43 PDT
X-Mailer: YahooMailWebService/0.8.115.325013
References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
<1320273192.94365.YahooMailNeo@web121014.mail.ne1.yahoo.com>
<CALxbBHVgr+RD8T2NbZsrySPrL8OFtD8V7OHXfaOHrKfC8_nSnw@mail.gmail.com>
Message-ID: <1320274723.40397.YahooMailNeo@web121017.mail.ne1.yahoo.com>
Date: Wed, 2 Nov 2011 15:58:43 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CALxbBHVgr+RD8T2NbZsrySPrL8OFtD8V7OHXfaOHrKfC8_nSnw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="-71337780-78840345-1320274723=:40397"
X-Spam-Score: -0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.91.107 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 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: 1RLjlh-0001bu-DC
Subject: Re: [Bitcoin-development] Lock protocol version numbers
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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: Wed, 02 Nov 2011 22:58:50 -0000
---71337780-78840345-1320274723=:40397
Content-Type: text/plain; charset=us-ascii
Cool thread. I enjoyed reading that :) Thanks for sharing.
________________________________
From: Christian Decker <decker.christian@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Cc: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net>
Sent: Wednesday, November 2, 2011 10:42 PM
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Just for reference: https://github.com/bitcoin/bitcoin/pull/63
The issue resulted in my most useless pull request fixing two variables :-)
I second the use of sub_version_num as a Client and Version identifier.
Regards,
Chris
On Wed, Nov 2, 2011 at 11:33 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
Point taken.
>
>
>About the sub_version_num though. I prefer to let the field by defined clients however they wish, with just a guideline suggestion that IDENTIFIER VERSION is a format they should follow.
>
>
>The idea being that different projects would have different release scheduling schemes and it'd be restrictive to lock people into the popular major.minor system.
>
>
>So for the current bitcoin to find out the version number of other clients (if it was needed), it would have to parse the number from the string:
>
>
>"Satoshi 0.5"
>
>
>Although there would be little reason for this with a sane protocol versioning scheme.
>
>
>If we're agreed then I'll start on that BIP.
>
>
>
>________________________________
>From: Gavin Andresen <gavinandresen@gmail.com>
>To: Amir Taaki <zgenjix@yahoo.com>
>Sent: Wednesday, November 2, 2011 9:34 PM
>Subject: Re: [Bitcoin-development] Lock protocol version numbers
>
>Good idea.
>
>Sounds perfect for a BIP....
>
>
>On Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
>> Hey,
>> Can we lock the version numbers to be the protocol version (which changes
>> rarely) and instead use the sub_version_num field + revision number for
>> individual builds?
>
>--
>--
>Gavin Andresen
>
>
>
>------------------------------------------------------------------------------
>RSA(R) Conference 2012
>Save $700 by Nov 18
>Register now
>http://p.sf.net/sfu/rsa-sfdev2dev1
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
---71337780-78840345-1320274723=:40397
Content-Type: text/html; charset=us-ascii
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Cool thread. I enjoyed reading that :) Thanks for sharing.</span></div><div><br><span></span></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Christian Decker <decker.christian@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Amir Taaki <zgenjix@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net><br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, November 2, 2011 10:42 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Bitcoin-development]
Lock protocol version numbers<br></font><br><meta http-equiv="x-dns-prefetch-control" content="off"><div id="yiv842179741">Just for reference: <a rel="nofollow" target="_blank" href="https://github.com/bitcoin/bitcoin/pull/63">https://github.com/bitcoin/bitcoin/pull/63</a><br>The issue resulted in my most useless pull request fixing two variables :-)<br><br>I second the use of sub_version_num as a Client and Version identifier.<br>
<br>Regards,<br>Chris<br><br><div class="yiv842179741gmail_quote">On Wed, Nov 2, 2011 at 11:33 PM, Amir Taaki <span dir="ltr"><<a rel="nofollow" ymailto="mailto:zgenjix@yahoo.com" target="_blank" href="mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>></span> wrote:<br><blockquote class="yiv842179741gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div><span>Point taken.</span></div><div><br><span></span></div><div><span>About the sub_version_num though. I prefer to let the field by defined clients however they wish, with just a guideline suggestion that IDENTIFIER VERSION is a format they should follow.</span></div>
<div><br><span></span></div><div><span>The idea being that different projects would have different release scheduling schemes and it'd be restrictive to lock people into the popular major.minor system.</span></div><div>
<br><span></span></div><div><span>So for the current bitcoin to find out the version number of other clients (if it was needed), it would have to parse the number from the string:</span></div><div><br><span></span></div>
<div>
<span>"Satoshi 0.5"</span></div><div><br><span></span></div><div><span>Although there would be little reason for this with
a sane protocol versioning scheme.</span></div><div><br><span></span></div><div><span>If we're agreed then I'll start on that BIP.</span></div><div><br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt;">
<div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Gavin Andresen <<a rel="nofollow" ymailto="mailto:gavinandresen@gmail.com" target="_blank" href="mailto:gavinandresen@gmail.com">gavinandresen@gmail.com</a>><br>
<b><span style="font-weight:bold;">To:</span></b> Amir Taaki <<a rel="nofollow" ymailto="mailto:zgenjix@yahoo.com" target="_blank" href="mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>><br><b><span style="font-weight:bold;">Sent:</span></b> Wednesday, November 2, 2011 9:34 PM<br>
<b><span style="font-weight:bold;">Subject:</span></b> Re: [Bitcoin-development] Lock protocol version numbers<br></font><br>
Good idea.<br><br>Sounds perfect for a BIP....<div class="yiv842179741im"><br><br>On Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki <<a rel="nofollow" ymailto="mailto:zgenjix@yahoo.com" target="_blank" href="mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>> wrote:<br>> Hey,<br>> Can we lock the version numbers to be the protocol version (which changes<br>
> rarely) and instead use the sub_version_num field + revision number for<br>> individual builds?<br><br></div><span class="yiv842179741HOEnZb"><font color="#888888">-- <br>--<br>Gavin Andresen<br><br><br></font></span></div></div>
</div></div><br>------------------------------------------------------------------------------<br>
RSA(R) Conference 2012<br>
Save $700 by Nov 18<br>
Register now<br>
<a rel="nofollow" target="_blank" href="http://p.sf.net/sfu/rsa-sfdev2dev1">http://p.sf.net/sfu/rsa-sfdev2dev1</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a rel="nofollow" ymailto="mailto:Bitcoin-development@lists.sourceforge.net" target="_blank" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a rel="nofollow" target="_blank" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br></blockquote></div><br>
</div><meta http-equiv="x-dns-prefetch-control" content="on"><br><br></div></div></div></body></html>
---71337780-78840345-1320274723=:40397--
|
