From: "Luke-Jr" <luke@dashjr•org>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD
Date: Wed, 21 Dec 2011 12:37:39 -0500 [thread overview]
Message-ID: <201112211237.40206.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpexr66ahs_+NtuGFNmQvmkp2J5HMCt3j2ysHL=1N-mS3w@mail.gmail.com>
On Wednesday, December 21, 2011 12:17:57 PM Jeff Garzik wrote:
> On Wed, Dec 21, 2011 at 12:14 PM, Luke-Jr <luke@dashjr•org> wrote:
> > On Wednesday, December 21, 2011 12:12:43 PM Jeff Garzik wrote:
> >> On Wed, Dec 21, 2011 at 11:45 AM, Luke-Jr <luke@dashjr•org> wrote:
> >> > Accepted for 0.6:
> >> > * 81807c3 (pull 719) Coinbaser
> >>
> >> This is not "accepted" as discussed yesterday on IRC. You need to
> >> find buy-in from some other miners to make sure this is what "they"
> >> want, rather than just what "you" want.
> >
> > It was per Gavin on IRC before yesterday.
>
> Quoting IRC yesterday,
> <gavinandresen> jgarzik: I defer to your judgement on coinbaser, I don't
> care.
[Friday, December 02, 2011] [1:57:14 PM] <gavinandresen> luke-jr: ok-- there
seems to be general consensus to pull coinbaser for 0.6, so I'll probably pull
it before op_eval and rework the op_eval code to use coinbaser.
> > And there is already buy-in from other miners.
>
> Then post data backing up that vague statement.
At least Eclipse (235 GH/s) is using it, and slush (1.3 TH/s) intends to.
next prev parent reply other threads:[~2011-12-21 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 20:49 Gavin Andresen
2011-12-21 1:46 ` Luke-Jr
2011-12-21 10:12 ` Mike Hearn
2011-12-21 15:44 ` Luke-Jr
2011-12-21 16:45 ` Luke-Jr
2011-12-21 17:12 ` Jeff Garzik
2011-12-21 17:14 ` Luke-Jr
2011-12-21 17:17 ` Jeff Garzik
2011-12-21 17:37 ` Luke-Jr [this message]
2011-12-21 10:30 ` Wladimir
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=201112211237.40206.luke@dashjr.org \
--to=luke@dashjr$(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