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
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
|
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 <decker.christian@gmail.com>) id 1RLjWi-0007wd-Or
for bitcoin-development@lists.sourceforge.net;
Wed, 02 Nov 2011 22:43:20 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175;
envelope-from=decker.christian@gmail.com;
helo=mail-wy0-f175.google.com;
Received: from mail-wy0-f175.google.com ([74.125.82.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RLjWg-0001B1-BD
for bitcoin-development@lists.sourceforge.net;
Wed, 02 Nov 2011 22:43:20 +0000
Received: by wyh5 with SMTP id 5so1015084wyh.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 02 Nov 2011 15:43:12 -0700 (PDT)
Received: by 10.227.198.141 with SMTP id eo13mr8217921wbb.19.1320273792146;
Wed, 02 Nov 2011 15:43:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.37.214 with HTTP; Wed, 2 Nov 2011 15:42:31 -0700 (PDT)
In-Reply-To: <1320273192.94365.YahooMailNeo@web121014.mail.ne1.yahoo.com>
References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
<1320273192.94365.YahooMailNeo@web121014.mail.ne1.yahoo.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Wed, 2 Nov 2011 23:42:31 +0100
Message-ID: <CALxbBHVgr+RD8T2NbZsrySPrL8OFtD8V7OHXfaOHrKfC8_nSnw@mail.gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: multipart/alternative; boundary=0015174c19e8631e3704b0c832d1
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
(decker.christian[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: 1RLjWg-0001B1-BD
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Lock protocol version numbers
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: Wed, 02 Nov 2011 22:43:20 -0000
--0015174c19e8631e3704b0c832d1
Content-Type: text/plain; charset=ISO-8859-1
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
>
>
--0015174c19e8631e3704b0c832d1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Just for reference: <a href=3D"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=3D"gmail_quote">On Wed, Nov 2, 2011=
at 11:33 PM, Amir Taaki <span dir=3D"ltr"><<a href=3D"mailto:zgenjix@ya=
hoo.com">zgenjix@yahoo.com</a>></span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex;">
<div><div style=3D"color:#000;background-color:#fff;font-family:times new r=
oman, 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 thou=
gh. I prefer to let the field by defined clients however they wish, with ju=
st a guideline suggestion that IDENTIFIER VERSION is a format they should f=
ollow.</span></div>
<div><br><span></span></div><div><span>The idea being that different projec=
ts would have different release scheduling schemes and it'd be restrict=
ive 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 th=
e version number of other clients (if it was needed), it would have to pars=
e 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></di=
v><div><br></div><div style=3D"font-family:times new roman, new york, times=
, serif;font-size:12pt">
<div style=3D"font-family:times new roman, new york, times, serif;font-size=
:12pt"><font face=3D"Arial" size=3D"2"><hr size=3D"1"><b><span style=3D"fon=
t-weight:bold">From:</span></b> Gavin Andresen <<a href=3D"mailto:gavina=
ndresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a>><br>
<b><span style=3D"font-weight:bold">To:</span></b> Amir Taaki <<a href=
=3D"mailto:zgenjix@yahoo.com" target=3D"_blank">zgenjix@yahoo.com</a>><b=
r><b><span style=3D"font-weight:bold">Sent:</span></b> Wednesday, November =
2, 2011 9:34 PM<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: [Bitcoin-develo=
pment] Lock protocol version numbers<br></font><br>
Good idea.<br><br>Sounds perfect for a BIP....<div class=3D"im"><br><br>On =
Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki <<a href=3D"mailto:zgenjix@yahoo=
.com" target=3D"_blank">zgenjix@yahoo.com</a>> wrote:<br>> Hey,<br>&g=
t; Can we lock the version numbers to be the protocol version (which change=
s<br>
> rarely) and instead use the sub_version_num field + revision number fo=
r<br>> individual builds?<br><br></div><span class=3D"HOEnZb"><font colo=
r=3D"#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 href=3D"http://p.sf.net/sfu/rsa-sfdev2dev1" target=3D"_blank">http://p.s=
f.net/sfu/rsa-sfdev2dev1</a><br>___________________________________________=
____<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br>
--0015174c19e8631e3704b0c832d1--
|
