Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1WLhGa-00053K-T4
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Mar 2014 22:59:52 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.41 as permitted sender)
	client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f41.google.com; 
Received: from mail-oa0-f41.google.com ([209.85.219.41])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WLhGa-0000af-5y
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Mar 2014 22:59:52 +0000
Received: by mail-oa0-f41.google.com with SMTP id j17so3392540oag.28
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 06 Mar 2014 14:59:46 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.136.170 with SMTP id qb10mr7940084oeb.34.1394146786885;
	Thu, 06 Mar 2014 14:59:46 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Thu, 6 Mar 2014 14:59:46 -0800 (PST)
In-Reply-To: <CABjHNoQQUu0WDdgFHAe4FEGmO8JmjvwAfpCwcrL7wGsHiVDjog@mail.gmail.com>
References: <CABjHNoQQUu0WDdgFHAe4FEGmO8JmjvwAfpCwcrL7wGsHiVDjog@mail.gmail.com>
Date: Thu, 6 Mar 2014 23:59:46 +0100
X-Google-Sender-Auth: 4SZuRLvyL7xHgN4Nmb8ZO-FqpJE
Message-ID: <CANEZrP1dSTbq==fjspaE0ktBMwhwOz2ByLDTiaOy_E2mS7_Wyw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: William Swanson <swansontec@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b33c94cff451e04f3f81775
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1WLhGa-0000af-5y
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bip-0021 and bip-0072 ambiguities &
	mistakes
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: Thu, 06 Mar 2014 22:59:53 -0000

--047d7b33c94cff451e04f3f81775
Content-Type: text/plain; charset=UTF-8

Yes please, pull req would be great! I also noticed that escaping doesn't
seem to be necessary, and the resultant de-escaped QRcodes are certainly
much nicer! Thanks!

--047d7b33c94cff451e04f3f81775
Content-Type: text/html; charset=UTF-8

<div dir="ltr">Yes please, pull req would be great! I also noticed that escaping doesn&#39;t seem to be necessary, and the resultant de-escaped QRcodes are certainly much nicer! Thanks!<div class="gmail_extra"><br></div></div>

--047d7b33c94cff451e04f3f81775--