public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Michael Grønager" <gronager@ceptacle.com>
To: Aidan Thornton <makosoft@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.5.2 tag in github ??
Date: Fri, 3 Feb 2012 10:59:01 +0100	[thread overview]
Message-ID: <9B2FB922-A86B-4189-926C-C6DB51A1C17F@ceptacle.com> (raw)
In-Reply-To: <CAB=c7Tp9Mu_-kux8gazysKVFHZaWZdEgsmoOVE+wz-AGYdN-XQ@mail.gmail.com>

Hi Aidan,

Thanks, and the number is still 140700 - do we have a policy / logic on adding new checkpoints ? It seems to me that the number could easily be bumped to 160000 by now ?

Cheers,

Michael
 
On 03/02/2012, at 10:52, Aidan Thornton wrote:

> On Fri, Feb 3, 2012 at 9:22 AM, Michael Grønager <gronager@ceptacle.com> wrote:
>> 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
> 
> I think that tag's in
> https://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable
> - a certain amount of developer politics seems to be involved, and
> v0.5.2 may not have been pushed to the official github repository.

Michael Gronager, PhD
Director, Ceptacle
Jens Juels Gade 33
2100 Copenhagen E
Mobile: +45 31 45 14 01
E-mail: gronager@ceptacle.com
Web: http://www.ceptacle.com/




  reply	other threads:[~2012-02-03  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  9:22 [Bitcoin-development] 0.5.2 tag in github ?? Michael Grønager
2012-02-03  9:52 ` Aidan Thornton
2012-02-03  9:59   ` Michael Grønager [this message]
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=9B2FB922-A86B-4189-926C-C6DB51A1C17F@ceptacle.com \
    --to=gronager@ceptacle.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=makosoft@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