From: Mike Hearn <mike@plan99•net>
To: William Swanson <swansontec@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bip-0021 and bip-0072 ambiguities & mistakes
Date: Thu, 6 Mar 2014 23:59:46 +0100 [thread overview]
Message-ID: <CANEZrP1dSTbq==fjspaE0ktBMwhwOz2ByLDTiaOy_E2mS7_Wyw@mail.gmail.com> (raw)
In-Reply-To: <CABjHNoQQUu0WDdgFHAe4FEGmO8JmjvwAfpCwcrL7wGsHiVDjog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
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!
[-- Attachment #2: Type: text/html, Size: 227 bytes --]
next prev parent reply other threads:[~2014-03-06 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 22:38 William Swanson
2014-03-06 22:59 ` Mike Hearn [this message]
2014-03-07 2:16 ` William Swanson
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='CANEZrP1dSTbq==fjspaE0ktBMwhwOz2ByLDTiaOy_E2mS7_Wyw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=swansontec@gmail$(echo .)com \
/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