Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <g.rowe.froot@gmail.com>) id 1Rt081-0002LS-Cg
	for bitcoin-development@lists.sourceforge.net;
	Thu, 02 Feb 2012 17:07:21 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.175 as permitted sender)
	client-ip=209.85.213.175; envelope-from=g.rowe.froot@gmail.com;
	helo=mail-yx0-f175.google.com; 
Received: from mail-yx0-f175.google.com ([209.85.213.175])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1Rt07x-0008TM-HZ
	for bitcoin-development@lists.sourceforge.net;
	Thu, 02 Feb 2012 17:07:21 +0000
Received: by yenr5 with SMTP id r5so1355395yen.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 02 Feb 2012 09:07:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.236.115.231 with SMTP id e67mr5702037yhh.16.1328202432215;
	Thu, 02 Feb 2012 09:07:12 -0800 (PST)
Sender: g.rowe.froot@gmail.com
Received: by 10.236.195.99 with HTTP; Thu, 2 Feb 2012 09:07:12 -0800 (PST)
Date: Thu, 2 Feb 2012 17:07:12 +0000
X-Google-Sender-Auth: kFsxpg-Tldu649YcTSvYIQKXO9Q
Message-ID: <CAKm8k+3V-sv4FdE1zFsB0xjDS1hfhdhGtUB=gYprOfvRO8Cuvg@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf303b434f297a5904b7fe3afc
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
	(g.rowe.froot[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: 1Rt07x-0008TM-HZ
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
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, 02 Feb 2012 17:07:21 -0000

--20cf303b434f297a5904b7fe3afc
Content-Type: text/plain; charset=UTF-8

BlueMatt, did the BIP0021 Wiki entry for "req:" to "req-" get updated? I'm
looking there now and it seems to be still at "req:"

--20cf303b434f297a5904b7fe3afc
Content-Type: text/html; charset=UTF-8

BlueMatt, did the BIP0021 Wiki entry for &quot;req:&quot; to &quot;req-&quot; get updated? I&#39;m looking there now and it seems to be still at &quot;req:&quot;<br>

--20cf303b434f297a5904b7fe3afc--