From: Gregory Maxwell <gmaxwell@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 22 - getmemorypool
Date: Mon, 30 Jul 2012 16:32:25 -0400 [thread overview]
Message-ID: <CAAS2fgQcGoEpD74S0SaiNxOe0NiLmUWqbJ14zPNp+AUCmueLaw@mail.gmail.com> (raw)
In-Reply-To: <1343679972.9880.YahooMailNeo@web121004.mail.ne1.yahoo.com>
On Mon, Jul 30, 2012 at 4:26 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
> Hi,
>
> luke-jr wants me to split this BIP into 3 separate BIPs because he says that other devs felt it was too unfocused and covered too many topics. However this discussion took place on IRC, a
It actually took place on this list:
http://sourceforge.net/mailarchive/forum.php?thread_name=20120612105038.GA29784%40vps7135.xlshosting.net&forum_name=bitcoin-development
It just took some IRC prodding to get Luke to move in the direction of
breaking it up to get the optional parts that Pieter objected to out
of the spec.
Perhaps other people missed it too... so discussing it more sounds
fine if anyone objects.
prev parent reply other threads:[~2012-07-30 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 20:26 [Bitcoin-development] BIP 22 - getmemorypool Amir Taaki
2012-07-30 20:30 ` Luke-Jr
2012-07-30 20:32 ` Gregory Maxwell [this message]
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=CAAS2fgQcGoEpD74S0SaiNxOe0NiLmUWqbJ14zPNp+AUCmueLaw@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=zgenjix@yahoo.com \
/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