From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [PULL] Wallet Private Key Encryption Take 3
Date: Tue, 28 Jun 2011 03:33:46 +0200 [thread overview]
Message-ID: <1309224826.3689.6.camel@Desktop666> (raw)
In-Reply-To: <1309137623.3689.4.camel@Desktop666>
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
OK, after a lot of good discussion and a tiny bit of results, I would
submit that Wallet Encryption is in a pull-able state. Can I get final
comments/ACKs
Matt
On Mon, 2011-06-27 at 03:20 +0200, Matt Corallo wrote:
> Rebased onto wallet class and ready for "wtf is this crap" messages ;)
>
> https://github.com/bitcoin/bitcoin/pull/352
>
> Matt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-06-28 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 1:20 Matt Corallo
2011-06-28 1:33 ` Matt Corallo [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=1309224826.3689.6.camel@Desktop666 \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.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