public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD
Date: Tue, 20 Dec 2011 20:46:41 -0500	[thread overview]
Message-ID: <201112202046.42905.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T3u5onesvWr46ZnKCsYAnxxoLn38PuL6K7RrYqmX8pQHw@mail.gmail.com>

On Tuesday, December 20, 2011 3:49:16 PM Gavin Andresen wrote:
> I've been busy pulling patches into git HEAD for a Bitcoin version
> 0.6, with the goal of having a Release Candidate 1 out in a couple of
> weeks.

I've rebuilt my 'next' and 'next-test' branches...
    git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin.git

Accepted for 0.6:
* 81807c3 Merge branch 'coinbaser' into next
* 6ea6db3 Merge remote branch 'laanwj/ui_copy_amount' into next
* a6ef83e Merge 'QR Code generation via libqrencode' into next
* e0673bd Merge branch 'signmessage_gui' into next

Ready for acceptance?
* 4783528 Merge remote branch 'matt/keepnode' into next-test
* 5a11d0f Merge branch 'force_send' into next-test
* 2cddc71 Merge remote branch 'sipa/comprpubkey' into next-test
* 73a8ca6 Merge remote branch 'matt/uri' into next-test
* 9314427 Merge remote branch 'gavin/testnetdifficulty' into next-test
* 1360e43 Merge branch 'stdint' into next-test

Needs review:
* 6ee82ff Merge branch 'forceresendtx' into next-test
* 8a82ba6 Merge branch 'blknotify' into next-test
* 674f1a6 Merge 'Temporarily disable "minimize to tray" in the startup phase
          if the "-min" option is specified' into next-test
* 5afd4de Merge branch 'bugfix_client_name' into next-test

Cannot be merged cleanly (at least not into next-test at this point):
* Pull 556 txinfo
* Pull 568 JSON-RPC multithreading + rpc_keepalive
* Pull 457 IPv6 JSON-RPC
* Pull 427 IPv6
* Pull 565 optimize_FastGetWork
* Pull 430 joelkatz optimizations
* Pull 562 optimize_ToHex
* Pull 452 JSON-RPC API versioning

Not yet written:
* Treat generation (almost) like normal receive
* JSON-RPC with integer amounts



  reply	other threads:[~2011-12-21  1:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 20:49 [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD Gavin Andresen
2011-12-21  1:46 ` Luke-Jr [this message]
2011-12-21 10:12   ` Mike Hearn
2011-12-21 15:44     ` Luke-Jr
2011-12-21 16:45   ` Luke-Jr
2011-12-21 17:12     ` Jeff Garzik
2011-12-21 17:14       ` Luke-Jr
2011-12-21 17:17         ` Jeff Garzik
2011-12-21 17:37           ` Luke-Jr
2011-12-21 10:30 ` 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=201112202046.42905.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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