From: Wladimir <laanwj@gmail•com>
To: Matt Corallo <bitcoin-list@bluematt•me>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] ACK NACK utACK "Concept ACK"
Date: Wed, 10 Dec 2014 08:21:00 +0000 [thread overview]
Message-ID: <CA+s+GJA0BDMaa2+A7QJdz08Ck4PFQcXs2dg22hi5PCMsGu7dqw@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJAe9MeO+Sr0+2BRwu3q-Be5JQt_s_xdnBBEcquXqOyxcA@mail.gmail.com>
On Wed, Dec 10, 2014 at 6:47 AM, Wladimir <laanwj@gmail•com> wrote:
> Abbreviations:
>
> Concept ACK -> agree with the idea and overall direction, but haven't
> reviewed the code changes nor tested it
> utACK -> reviewed the code changes, but did not put it through any testing
> Tested ACK -> reviewed the code changes and verified the functionality/bug fix
And there is also NACK, that's an aspecific 'I wouldn't like this
merged'. I always explain why in the text.
A document on this would be welcome, as it may look like Martian to
outsiders. That's been brought up many times before, but no one ever
created it.
Wladimir
next prev parent reply other threads:[~2014-12-10 8:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 21:14 Sergio Lerner
2014-12-09 21:30 ` Matt Corallo
2014-12-10 6:47 ` Wladimir
2014-12-10 7:35 ` [Bitcoin-development] Merged mining a side chain with proof of burn on parent chain Tamas Blummer
2014-12-10 8:30 ` patrick
2014-12-16 9:55 ` Alex Mizrahi
2014-12-16 12:36 ` Peter Todd
2014-12-15 14:55 ` Isidor Zeuner
2014-12-16 8:28 ` Tamas Blummer
2014-12-16 12:30 ` Tamas Blummer
2014-12-18 16:23 ` Tamas Blummer
2014-12-10 8:21 ` Wladimir [this message]
2014-12-10 15:45 ` [Bitcoin-development] ACK NACK utACK "Concept ACK" Austin Walne
2014-12-17 8:44 ` Wladimir
2014-12-10 15:52 ` Jeff Garzik
2014-12-16 23:40 ` Btc Drak
2014-12-11 12:09 ` [Bitcoin-development] Merged mining a side chain with proof of burn on parent chain Isidor Zeuner
2014-12-11 14:56 ` Tamas Blummer
2014-12-15 10:21 ` Tamas Blummer
2014-12-15 12:39 ` Peter Todd
2014-12-15 13:06 ` Tamas Blummer
2015-02-04 13:54 ` Isidor Zeuner
2015-02-06 1:34 ` Peter Todd
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=CA+s+GJA0BDMaa2+A7QJdz08Ck4PFQcXs2dg22hi5PCMsGu7dqw@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/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