From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.4rc1 known bugs
Date: Tue, 6 Sep 2011 16:55:27 -0400 [thread overview]
Message-ID: <201109061655.30148.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T1juB-0hr9NW=PoO5eh_Aqhzkiv3tnXTSTsjBKiy4y0JA@mail.gmail.com>
Got a fix for the encrypted-wallet mining issue:
- unique_coinbase
It depends on (and merges) the getwork_dedupe fix already common on pools and
other miners who pay attention to the latest mining fixes.
To merge:
git fetch git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin.git \
unique_coinbase && git merge FETCH_HEAD
next prev parent reply other threads:[~2011-09-06 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 0:13 [Bitcoin-development] 0.4rc1 known bugs Gavin Andresen
2011-09-04 2:43 ` Matt Corallo
2011-09-05 7:25 ` Michael Grønager
2011-09-05 12:42 ` Luke-Jr
2011-09-05 12:47 ` Michael Grønager
[not found] ` <20110904115926.GA16476@ulyssis.org>
2011-09-06 11:55 ` Pieter Wuille
2011-09-06 17:59 ` Gavin Andresen
2011-09-06 20:55 ` Luke-Jr [this message]
2011-09-07 15:07 ` Gavin Andresen
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=201109061655.30148.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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