diff options
author | Matt Corallo <bitcoin-list@bluematt.me> | 2011-08-29 21:09:03 -0400 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2011-08-30 01:09:13 +0000 |
commit | 9ffb8ecaac877c906c63e21ba6307904521026d2 (patch) | |
tree | 448f1943c638842241cfab7e62722667ad8fbd53 /ff | |
parent | 85d8a0ba6982c5ae2cbd953954e434ebdfe6c8f5 (diff) | |
download | pi-bitcoindev-9ffb8ecaac877c906c63e21ba6307904521026d2.tar.gz pi-bitcoindev-9ffb8ecaac877c906c63e21ba6307904521026d2.zip |
Re: [Bitcoin-development] Project status
Diffstat (limited to 'ff')
-rw-r--r-- | ff/f2450cde8331674bad27b268a58ed20792d091 | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/ff/f2450cde8331674bad27b268a58ed20792d091 b/ff/f2450cde8331674bad27b268a58ed20792d091 new file mode 100644 index 000000000..624cea62f --- /dev/null +++ b/ff/f2450cde8331674bad27b268a58ed20792d091 @@ -0,0 +1,77 @@ +Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <bitcoin-list@bluematt.me>) id 1QyCpF-0000Mk-67 + for bitcoin-development@lists.sourceforge.net; + Tue, 30 Aug 2011 01:09:13 +0000 +Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me + designates 173.246.101.161 as permitted sender) + client-ip=173.246.101.161; + envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; +Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me) + by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1QyCpD-0007lP-08 for bitcoin-development@lists.sourceforge.net; + Tue, 30 Aug 2011 01:09:13 +0000 +Received: from [192.168.1.2] (dhcp04346.highsouth-resnet.unc.edu + [152.23.97.28]) + by mail.bluematt.me (Postfix) with ESMTPSA id AF18DBB4 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 30 Aug 2011 03:07:28 +0200 (CEST) +From: Matt Corallo <bitcoin-list@bluematt.me> +To: bitcoin-development@lists.sourceforge.net +In-Reply-To: <CABsx9T20JDnt5xF24HbJdhHe=MFZ3PDyk2cE+Q4V8iC0rgbASg@mail.gmail.com> +References: <CABsx9T20JDnt5xF24HbJdhHe=MFZ3PDyk2cE+Q4V8iC0rgbASg@mail.gmail.com> +Content-Type: text/plain; charset="UTF-8" +Date: Mon, 29 Aug 2011 21:09:03 -0400 +Message-ID: <1314666543.5889.2.camel@BMThinkPad.lan.bluematt.me> +Mime-Version: 1.0 +X-Mailer: Evolution 2.32.2 +Content-Transfer-Encoding: 7bit +X-Spam-Score: -2.0 (--) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + -0.0 SPF_PASS SPF: sender matches SPF record + -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain 0.0 AWL AWL: From: address is in the auto white-list +X-Headers-End: 1QyCpD-0007lP-08 +Subject: Re: [Bitcoin-development] Project status +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Tue, 30 Aug 2011 01:09:13 -0000 + +On Mon, 2011-08-29 at 16:10 -0400, Gavin Andresen wrote: +> Quick brain dump on a bunch of stuff: +> +> I'd like to get a 0.4 release out, but am still working on a fix for +> the deadlock bugs that the new wallet encryption and/or the CWallet +> refactoring caused. My short-term plan is to reduce the number of +> locks and make sure they're always acquired in a consistent order. +> Longer term, I think reworking the design to be based on +> boost::asio and use fewer threads is probably the right thing to do. +Hopefully working on something that would help do this now. +> +> Other things on the 0.4 TODO list: block chain checkpoint (got a PULL +> for that, thanks). Updated list of hard-coded seed nodes (nanotube +> did that last time). Pieter's dump/import privkey patch. +Also my build update pull would be much appreciated. +> +> After my talk at the conference, Alex Waters approached me about being +> the core bitcoin Q/A lead; he'll be working on creating test plans, +> keeping on top of the issues list, testing new features, and +> suggesting improvements to the code/test/release process. And +> whatever else he thinks needs to be done to improve core bitcoin. +NICE + + + |