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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9FD2A1BB
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 27 Nov 2015 10:14:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f48.google.com (mail-vk0-f48.google.com
[209.85.213.48])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0AE89170
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 27 Nov 2015 10:14:10 +0000 (UTC)
Received: by vkca188 with SMTP id a188so10429429vkc.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 27 Nov 2015 02:14:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=JBsX1WeYMBykU2hwP9KLl+HNsEE7MbsoEcI1fjk/y6s=;
b=LGf7kfcioKIlDal/Nz6SEOyw2INtQKHvS0RHt8DfjFIu78xNQ62QqtocvG8EJAzhNq
tQqEW8WfxsW/8choae1Rv7BJJLksNAG4UhOC1FZWDsHvkAK4/AIXorJTa7hihAsWKxUA
i0oV0pi93nxqoFKPNQCbXjYnjIY04bYvSkJ3vCMk17Kp1PddGPN2hLumM8qtOnGqPAw6
4NSrFeKxkC0Lvl7d5rPdEMkmrupPGbVWJxGrGAz3li1U8p+7y638l8Al39jxUWltwdxa
NFrpbzIen+zVay43WCrqXWw/LOdPkEl8KAs+a/rOezbi878DoNig4HzyaV3GZDSEriK4
PkYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=JBsX1WeYMBykU2hwP9KLl+HNsEE7MbsoEcI1fjk/y6s=;
b=jnULiP4ujyvtDC/Sr72sSvZslM1kiyt78r+6jzaMiUiGlgGmDZYdxqz7CQyQNMT0rN
UW1z3ZratDKW2tcUNl6S8SyQ18JA0l95Nwm9whk9ASCK4IJhHSx5GmnMbnsCw+mKc2c4
zbeS3uuq0tkCFus6Aio3wNqCnj0cEd8D/W8blLFEs59hD/8mlzKzEgxGjnfR7MUwrqoC
C+tnD8y5ur3coSAjfyRjiInY+E/aX6ZK0M0M4kjv3YBCI8g9cv8AAlKoIJI0JRvarPqQ
C2PNJmk48a/+PlLGLlnlABTWEtNBQ8oWA+QmHtiZ3ztiVCLz+OoIOLMqdX05JVe1Qr0u
h1cQ==
X-Gm-Message-State: ALoCoQmdvyPfWSgZN8N4WS2u1syexGW5A6cm8Vm+Kmm/NQ37TZ44Q4/mH43PUKIPNQTLy+039LYc
MIME-Version: 1.0
X-Received: by 10.31.34.196 with SMTP id i187mr41951776vki.2.1448619250272;
Fri, 27 Nov 2015 02:14:10 -0800 (PST)
Received: by 10.31.236.70 with HTTP; Fri, 27 Nov 2015 02:14:10 -0800 (PST)
Received: by 10.31.236.70 with HTTP; Fri, 27 Nov 2015 02:14:10 -0800 (PST)
In-Reply-To: <CAOG=w-v0_dfZS2=XfKQzRZ9Vq2Z2YqUO2_cuvOheuUrD4dbYtw@mail.gmail.com>
References: <CADJgMzs0w4L7ma42RCzT5dYDcG2aY1_04G1khcFPFPE6mmB=-A@mail.gmail.com>
<CAOG=w-v0_dfZS2=XfKQzRZ9Vq2Z2YqUO2_cuvOheuUrD4dbYtw@mail.gmail.com>
Date: Fri, 27 Nov 2015 11:14:10 +0100
Message-ID: <CABm2gDrjiNTNo3FZ82D3131g5gBEwfHCofdK9BeEPPZ6k-TzbQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Mark <mark@friedenbach.org>
Content-Type: multipart/alternative; boundary=001a113daab6d40e99052582f3cf
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 27 Nov 2015 11:10:43 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2015 10:14:11 -0000
--001a113daab6d40e99052582f3cf
Content-Type: text/plain; charset=UTF-8
On Nov 26, 2015 12:06 AM, "Mark Friedenbach via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Again my objection would go away if we renamed nSequence, but I actually
think the nSequence name is better...
I suggested to rename nSequence to nMaturity on this list even before the
bips and implementations were started, probably too late now.
Before the implementation "let's think about those naming details later".
After the implementation "now it's too late, now we would need to change
the implementation, this renaming is now unnecessarily disruptive".
Reminds me of refactors and major releases:
At the beginning of the release "not now, this will disrupt development of
feature X"
After feature X is merged or replaced by feature Y: "too late in the
release cycle, refactors should be done only at the beginning, at the end
is 'too risky' ".
Sigh, I hope I find the "right time" (not both too soon and too late like
this time), next time...
--001a113daab6d40e99052582f3cf
Content-Type: text/html; charset=UTF-8
<p dir="ltr"><br>
On Nov 26, 2015 12:06 AM, "Mark Friedenbach via bitcoin-dev" <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> Again my objection would go away if we renamed nSequence, but I actually think the nSequence name is better...</p>
<p dir="ltr">I suggested to rename nSequence to nMaturity on this list even before the bips and implementations were started, probably too late now.<br>
Before the implementation "let's think about those naming details later".<br>
After the implementation "now it's too late, now we would need to change the implementation, this renaming is now unnecessarily disruptive".</p>
<p dir="ltr">Reminds me of refactors and major releases:<br>
At the beginning of the release "not now, this will disrupt development of feature X"<br>
After feature X is merged or replaced by feature Y: "too late in the release cycle, refactors should be done only at the beginning, at the end is 'too risky' ".<br>
Sigh, I hope I find the "right time" (not both too soon and too late like this time), next time...</p>
--001a113daab6d40e99052582f3cf--
|
