From: "Jorge Timón" <jtimon@jtimon•cc>
To: Mark <mark@friedenbach•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)
Date: Fri, 27 Nov 2015 11:14:10 +0100 [thread overview]
Message-ID: <CABm2gDrjiNTNo3FZ82D3131g5gBEwfHCofdK9BeEPPZ6k-TzbQ@mail.gmail.com> (raw)
In-Reply-To: <CAOG=w-v0_dfZS2=XfKQzRZ9Vq2Z2YqUO2_cuvOheuUrD4dbYtw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
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...
[-- Attachment #2: Type: text/html, Size: 1186 bytes --]
prev parent reply other threads:[~2015-11-27 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 10:30 Btc Drak
2015-11-24 12:20 ` Peter Todd
2015-11-24 12:35 ` Jorge Timón
2015-11-24 12:31 ` Jorge Timón
2015-11-25 1:14 ` Eric Lombrozo
2015-11-26 21:32 ` Eric Lombrozo
2015-11-26 22:25 ` Peter Todd
2015-11-25 23:05 ` Mark Friedenbach
2015-11-25 23:41 ` Eric Lombrozo
2015-11-26 22:23 ` Matt Corallo
2015-11-27 4:02 ` Rusty Russell
2015-11-27 8:10 ` Eric Lombrozo
2015-11-27 4:08 ` Dave Scotese
2015-11-27 10:14 ` Jorge Timón [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABm2gDrjiNTNo3FZ82D3131g5gBEwfHCofdK9BeEPPZ6k-TzbQ@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=mark@friedenbach$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox