public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jim Nguyen <jimmy.winn@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [ANNOUNCE] BitCoinJ v0.2
Date: Mon, 27 Jun 2011 14:02:22 -0700	[thread overview]
Message-ID: <BANLkTi=iqPmbTrAPawQMG6isgYmnZzbSjw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimgmB-gviqWfLb6dNMAzzX8wYy7WQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]

This is great!  Good job guys!

Jim

On Mon, Jun 27, 2011 at 1:46 PM, Mike Hearn <mike@plan99•net> wrote:

> [also sent to bitcoin-development@]
>
> I'm pleased to announce BitCoinJ v0.2. There have been over 100 commits
> since the first release back in March, which have added:
>
>    - Full support for block chain re-orgs, including recognition of dead
>    transactions (that will never be included in the chain).
>    - Persistence of the block chain using multiple, pluggable stores. A
>    BoundedOverheadBlockStore is provided that is suitable for usage on mobile
>    devices where low memory usage and instant startup time are requirements.
>    - A much larger test suite
>    - IRC, DNS  and seed list peer discovery
>    - ASN.1 key export
>    - Many many bugfixes and minor API improvements.
>
> This release represents the work of many people. In particular I'd like to
> thank:
>
>    - Andreas Schildbach
>    - Miron Cuperman
>    - Gary Rowe
>    - Thilo Planz
>    - Micheal Swiggs
>    - Noa Resare
>    - John Sample
>    - Xiaofeng Guo
>
> --
> Google Switzerland GmbH
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 2250 bytes --]

      reply	other threads:[~2011-06-27 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 20:46 Mike Hearn
2011-06-27 21:02 ` Jim Nguyen [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='BANLkTi=iqPmbTrAPawQMG6isgYmnZzbSjw@mail.gmail.com' \
    --to=jimmy.winn@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=mike@plan99$(echo .)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