From: Jeff Garzik <jgarzik@exmulti.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Network version increase
Date: Mon, 2 Apr 2012 12:32:52 -0400 [thread overview]
Message-ID: <CA+8xBpep_gvX8Tp-srwFtvdzCyWFfXeR_e_P27CgVoXZj+frcQ@mail.gmail.com> (raw)
In-Reply-To: <20120402152259.GA19853@vps7135.xlshosting.net>
On Mon, Apr 2, 2012 at 11:23 AM, Pieter Wuille <pieter.wuille@gmail.com> wrote:
> Any opinions about a numbering scheme? Currently the value 60000 is used. We could
> simply start increasing the number one by one now for every change, or we could
> do a "cleanup" to 100000 first, and start incrementing from there.
It would be nice to have 100000 as the baseline, "frozen" protocol.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next prev parent reply other threads:[~2012-04-02 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 15:23 [Bitcoin-development] Network version increase Pieter Wuille
2012-04-02 16:32 ` Jeff Garzik [this message]
2012-04-02 16:42 ` Wladimir
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=CA+8xBpep_gvX8Tp-srwFtvdzCyWFfXeR_e_P27CgVoXZj+frcQ@mail.gmail.com \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pieter.wuille@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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