From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RdBGj-0006VA-MV for bitcoin-development@lists.sourceforge.net; Wed, 21 Dec 2011 01:46:57 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RdBGf-0002fc-KG for bitcoin-development@lists.sourceforge.net; Wed, 21 Dec 2011 01:46:57 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id D8583560514; Wed, 21 Dec 2011 01:46:47 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 20 Dec 2011 20:46:41 -0500 User-Agent: KMail/1.13.7 (Linux/3.1.4-gentoo; KDE/4.7.3; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112202046.42905.luke@dashjr.org> X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RdBGf-0002fc-KG Subject: Re: [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 01:46:57 -0000 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