From: Btc Drak <btcdrak@gmail•com>
To: Jeff Garzik <jgarzik@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] libconsensus and bitcoin development process
Date: Tue, 15 Sep 2015 19:26:50 +0100 [thread overview]
Message-ID: <CADJgMzuha2mA7VgmtdgsYmK8c0121MiEi52nKMNB0VPqFYNk4g@mail.gmail.com> (raw)
In-Reply-To: <CADm_WcafXgg5xpQjE8uSfp-2y59XRaCUr9w5yNEoVo6GygYzZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Tue, Sep 15, 2015 at 4:26 PM, Jeff Garzik <jgarzik@gmail•com> wrote:
> The problem comes with the impact of an unfocused stream of refactors to
> key code.
>
> For example, there is much less long term developer impact if refactoring
> were _accelerated_, scheduled to be performed in a one-week sprint. There
> is a lot of breakage, yes, but after that week the average level of
> downstream patch breakage is significantly lower. A "rip the band-aid off
> quickly rather than slowly" approach.
>
My sentiments exactly...
[-- Attachment #2: Type: text/html, Size: 890 bytes --]
next prev parent reply other threads:[~2015-09-15 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 4:10 Jeff Garzik
2015-09-15 9:55 ` Btc Drak
2015-09-15 15:26 ` Jeff Garzik
2015-09-15 16:00 ` Eric Lombrozo
2015-09-15 18:26 ` Btc Drak [this message]
2015-09-16 22:29 ` Peter Todd
2015-09-18 0:07 ` Wladimir J. van der Laan
2015-09-18 8:42 ` Eric Lombrozo
2015-09-18 16:22 ` Mike Hearn
2015-09-22 18:12 ` Jorge Timón
2015-09-22 23:49 ` Dave Scotese
2015-09-23 17:28 ` Jorge Timón
2015-09-29 13:04 ` Jeff Garzik
[not found] ` <CABsx9T0dHxXzemxJN87mU59j4_KZ=zOdwxpXOUe-NhB0ENVMWw@mail.gmail.com>
2015-09-23 16:58 ` Jorge Timón
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=CADJgMzuha2mA7VgmtdgsYmK8c0121MiEi52nKMNB0VPqFYNk4g@mail.gmail.com \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jgarzik@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