From: "Michael Grønager" <gronager@ceptacle•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.5.2 tag in github ??
Date: Fri, 3 Feb 2012 10:22:23 +0100 [thread overview]
Message-ID: <83F45CA3-D54A-499A-8A20-922CDEE52993@ceptacle.com> (raw)
Hi Gavin, others?
I am trying to redo the performance test of the libcoin client against the 0.5.2 Satoshi client, that I have learned also have received quite some improvements in speed since 0.4.0 (e.g. from not verifying signatures on early blocks).
However, I cannot find any tag with v0.5.2 in github:
https://github.com/bitcoin/bitcoin/tags
Am I missing something, or wasn't that release tagged ?
What I am looking for in particular is the number "140700", the last block not to be verified - I can see this in:
https://github.com/bitcoin/bitcoin/blob/master/src/checkpoints.cpp
But I would like to be sure that this is also the number used in 0.5.2.
Thanks,
Michael
next reply other threads:[~2012-02-03 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 9:22 Michael Grønager [this message]
2012-02-03 9:52 ` Aidan Thornton
2012-02-03 9:59 ` Michael Grønager
2012-02-03 13:45 ` Gregory Maxwell
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=83F45CA3-D54A-499A-8A20-922CDEE52993@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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