From: Christian Decker <decker.christian@gmail•com>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Date: Wed, 2 Nov 2011 22:32:10 +0100 [thread overview]
Message-ID: <CALxbBHXOO+p40Q_j7sPK+cG1yGyDWo3fT2_Nd8xhsWmoXD5LNA@mail.gmail.com> (raw)
In-Reply-To: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
I don't really get what you want to achieve with this. The protocol will be
slow down evolution (hopefully) soon, while the clients will continue
releasing at a similar rhythm. It took long enough to decouple the protocol
version from being bumped each client release, now doing the inverse
coupling makes no sense.
Regards,
Chris
On Wed, Nov 2, 2011 at 10: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?
>
> Satoshi 0.4
> BitcoinJava 120311
> bitcoin-js 6
>
> Like so. Otherwise we will have version bumping insanity :)
>
>
> ------------------------------------------------------------------------------
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 1800 bytes --]
next prev parent reply other threads:[~2011-11-02 21:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 21:23 Amir Taaki
2011-11-02 21:32 ` Christian Decker [this message]
[not found] ` <CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
2011-11-02 22:33 ` Amir Taaki
2011-11-02 22:42 ` Christian Decker
2011-11-02 22:58 ` Amir Taaki
2011-11-02 22:46 ` Luke-Jr
2011-11-02 22:55 ` Amir Taaki
2011-11-02 23:07 ` Luke-Jr
2011-11-02 23:22 ` Christian Decker
2011-11-03 4:46 ` Jeff Garzik
2011-11-05 14:32 ` Mike Hearn
2011-11-05 14:45 ` Christian Decker
[not found] ` <1320507570.40074.YahooMailNeo@web121017.mail.ne1.yahoo.com>
2011-11-05 15:39 ` Amir Taaki
2011-11-05 16:17 ` Christian Decker
2011-11-05 16:29 ` Luke-Jr
2011-11-05 16:40 ` Amir Taaki
2011-11-05 17:30 ` Jordan Mack
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=CALxbBHXOO+p40Q_j7sPK+cG1yGyDWo3fT2_Nd8xhsWmoXD5LNA@mail.gmail.com \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(echo .)com \
/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