From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1Y7pxU-0003Ql-53
	for bitcoin-development@lists.sourceforge.net;
	Sun, 04 Jan 2015 18:31:24 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.172 as permitted sender)
	client-ip=209.85.213.172; envelope-from=gmaxwell@gmail.com;
	helo=mail-ig0-f172.google.com; 
Received: from mail-ig0-f172.google.com ([209.85.213.172])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Y7pxO-0006q6-9o
	for bitcoin-development@lists.sourceforge.net;
	Sun, 04 Jan 2015 18:31:24 +0000
Received: by mail-ig0-f172.google.com with SMTP id hl2so762795igb.17
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 04 Jan 2015 10:31:13 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.30.204 with SMTP id e195mr75415040ioe.28.1420396272992; 
	Sun, 04 Jan 2015 10:31:12 -0800 (PST)
Received: by 10.107.16.30 with HTTP; Sun, 4 Jan 2015 10:31:12 -0800 (PST)
In-Reply-To: <54A98268.8030309@jrn.me.uk>
References: <54A95179.2070200@jrn.me.uk>
	<CAAS2fgSw=Goibe2LkXsEH5xjyftjQq4FxJh-dhaP_N5ea21ugQ@mail.gmail.com>
	<54A976C3.1030805@jrn.me.uk>
	<CAAS2fgTxwD2GJ-n+d=ovEYWCxpwyPO_DMBguP_ioc+_cdEhW=w@mail.gmail.com>
	<CAAS2fgROnDRbzNubLa588mXRJR4jwEBotvQi5bFm5dnNQxiwTA@mail.gmail.com>
	<54A98268.8030309@jrn.me.uk>
Date: Sun, 4 Jan 2015 18:31:12 +0000
Message-ID: <CAAS2fgT9Poj=OD9EyqpiPgTc_jB+EyLV+3ye5i65zHxF456zjw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Ross Nicoll <jrn@jrn.me.uk>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Y7pxO-0006q6-9o
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Re-enabling simple tx replacement
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 04 Jan 2015 18:31:24 -0000

On Sun, Jan 4, 2015 at 6:11 PM, Ross Nicoll <jrn@jrn.me.uk> wrote:
> Ah, thanks for that.
>
> I'll try Peter's patch for testnet tomorrow, sounds like it should fix
> this for my use case.

Thanks for presenting your solution as code in any case. In spite of
the fact that I gave it a crappy read this time, it really is a useful
way to communicate and I wish more people did that.