summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Schildbach <andreas@schildbach.de>2012-05-03 09:16:57 +0200
committerbitcoindev <bitcoindev@gnusha.org>2012-05-03 07:17:35 +0000
commit35870bc65ce97ebf26535f0b880a4b3fe9ecf6f7 (patch)
treed6b04a7b1b19fcb13b644c6e9db213b4dc37493d
parent3b13c8b2d197a4c51824d9a9bf78549c0e5a5fe0 (diff)
downloadpi-bitcoindev-35870bc65ce97ebf26535f0b880a4b3fe9ecf6f7.tar.gz
pi-bitcoindev-35870bc65ce97ebf26535f0b880a4b3fe9ecf6f7.zip
Re: [Bitcoin-development] URI Handling in Bitcoin-Qt
-rw-r--r--a2/8e8ae7c503942c86e6f12eb0baedc448db57f179
1 files changed, 79 insertions, 0 deletions
diff --git a/a2/8e8ae7c503942c86e6f12eb0baedc448db57f1 b/a2/8e8ae7c503942c86e6f12eb0baedc448db57f1
new file mode 100644
index 000000000..9cf2e498d
--- /dev/null
+++ b/a2/8e8ae7c503942c86e6f12eb0baedc448db57f1
@@ -0,0 +1,79 @@
+Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <gcbd-bitcoin-development@m.gmane.org>)
+ id 1SPqIB-0004fX-0Y for bitcoin-development@lists.sourceforge.net;
+ Thu, 03 May 2012 07:17:35 +0000
+Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of m.gmane.org
+ designates 80.91.229.3 as permitted sender)
+ client-ip=80.91.229.3;
+ envelope-from=gcbd-bitcoin-development@m.gmane.org;
+ helo=plane.gmane.org;
+Received: from plane.gmane.org ([80.91.229.3])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
+ (Exim 4.76) id 1SPqI6-0007eL-U5
+ for bitcoin-development@lists.sourceforge.net;
+ Thu, 03 May 2012 07:17:34 +0000
+Received: from list by plane.gmane.org with local (Exim 4.69)
+ (envelope-from <gcbd-bitcoin-development@m.gmane.org>)
+ id 1SPqHs-0003w1-Rg for bitcoin-development@lists.sourceforge.net;
+ Thu, 03 May 2012 09:17:16 +0200
+Received: from e179076037.adsl.alicedsl.de ([85.179.76.37])
+ by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
+ id 1AlnuQ-0007hv-00 for <bitcoin-development@lists.sourceforge.net>;
+ Thu, 03 May 2012 09:17:16 +0200
+Received: from andreas by e179076037.adsl.alicedsl.de with local (Gmexim 0.1
+ (Debian)) id 1AlnuQ-0007hv-00
+ for <bitcoin-development@lists.sourceforge.net>;
+ Thu, 03 May 2012 09:17:16 +0200
+X-Injected-Via-Gmane: http://gmane.org/
+To: bitcoin-development@lists.sourceforge.net
+From: Andreas Schildbach <andreas@schildbach.de>
+Date: Thu, 03 May 2012 09:16:57 +0200
+Message-ID: <jntbda$c1c$1@dough.gmane.org>
+References: <4FA2095D.9060307@gmail.com>
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 7bit
+X-Complaints-To: usenet@dough.gmane.org
+X-Gmane-NNTP-Posting-Host: e179076037.adsl.alicedsl.de
+User-Agent: Mozilla/5.0 (X11; Linux x86_64;
+ rv:11.0) Gecko/20120410 Thunderbird/11.0.1
+In-Reply-To: <4FA2095D.9060307@gmail.com>
+X-Spam-Score: -0.4 (/)
+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 SPF_HELO_PASS SPF: HELO matches SPF record
+ 1.1 DKIM_ADSP_ALL No valid author signature,
+ domain signs all mail
+ -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
+ domain
+ -0.0 SPF_PASS SPF: sender matches SPF record
+X-Headers-End: 1SPqI6-0007eL-U5
+Subject: Re: [Bitcoin-development] URI Handling in Bitcoin-Qt
+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, 03 May 2012 07:17:35 -0000
+
+On 05/03/2012 06:28 AM, Alan Reiner wrote:
+
+> *(3) *How are the other clients implementing this? Do you make any
+> distinction between "label" and "message"?
+
+Bitcoin Wallet for Android currently ignores both fields. At least
+temporarly displaying the transaction message is on my short-term todo list.
+
+
+
+