From: Mike Hearn <mike@plan99•net>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] LevelDB benchmarking
Date: Wed, 20 Jun 2012 14:41:30 +0200 [thread overview]
Message-ID: <CANEZrP3=0cJLjyUZ8FqmWXBRoiP-bzPzm14O=unmbDQ_=hHwVA@mail.gmail.com> (raw)
In-Reply-To: <20120620113744.GA14695@vps7135.xlshosting.net>
> Two days ago on #bitcoin-dev:
> 21:01:19< sipa> what was CTxDB::ReadOwnerTxes ever used for?
> 21:01:31< sipa> maybe it predates the wallet logic
>
> (read: it's not used anywhere in the code, and apparently wasn't ever, even in 0.1.5)
Great, in that case Stefan is right and I'll delete that code when I
next work on the patch.
next prev parent reply other threads:[~2012-06-20 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 18:41 Mike Hearn
[not found] ` <CAAS2fgTNqUeYy+oEFyQWrfs4Xyb=3NXutvCmLusknF-18JmFQg@mail.gmail.com>
2012-06-19 9:05 ` Mike Hearn
2012-06-19 11:38 ` Pieter Wuille
2012-06-19 15:05 ` Gavin Andresen
2012-06-19 16:06 ` Mike Hearn
2012-06-19 19:22 ` Stefan Thomas
2012-06-20 9:44 ` Mike Hearn
2012-06-20 9:53 ` Mike Hearn
2012-06-20 11:37 ` Pieter Wuille
2012-06-20 12:41 ` Mike Hearn [this message]
2012-06-25 16:32 ` Mike Hearn
2012-07-21 18:49 ` Mike Hearn
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='CANEZrP3=0cJLjyUZ8FqmWXBRoiP-bzPzm14O=unmbDQ_=hHwVA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@gmail$(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