From: Doug Huff <dhuff@jrbobdobbs•org>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] satoshi client v0.4 priorities
Date: Tue, 28 Jun 2011 13:39:22 -0500 [thread overview]
Message-ID: <41C9602E-0234-4357-9B75-E0A4DA65B117@jrbobdobbs.org> (raw)
In-Reply-To: <BANLkTin=_y_GGFO0JT9Z8jdmGwGEm7Yrvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
sipa already rebased his showwallet tree. It's missing the segfault fix (or was yesterday) but said fix merges cleanly. I'm not entirely sure it's ready for pulling but it is in a functional state.
On Jun 28, 2011, at 12:48 PM, Jeff Garzik wrote:
> (copying part of a conversation from IRC)
>
> IMO, wallet crypto and wallet import/export are the two "must have"
> features for v0.4. wallet crypto rationale is obvious. sipa's wallet
> import/export might need a rebase, but it seems important for further
> wallet security, such as printing out and storing a private key in a
> bank's safety deposit box.
>
> autotools and other stuff can wait, if they hold up the release of
> wallet crypto.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti•com
>
> ------------------------------------------------------------------------------
> 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
--
Doug Huff
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 881 bytes --]
next prev parent reply other threads:[~2011-06-28 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 17:48 Jeff Garzik
2011-06-28 18:39 ` Doug Huff [this message]
2011-06-28 19:50 ` Matt Corallo
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=41C9602E-0234-4357-9B75-E0A4DA65B117@jrbobdobbs.org \
--to=dhuff@jrbobdobbs$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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