blob: 6a6a0620080efc81c2f773dbc35b4f7128c3e792 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
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 <aaxiomfinity@gmail.com>) id 1Vtupq-0005OJ-6h
for bitcoin-development@lists.sourceforge.net;
Fri, 20 Dec 2013 07:49:26 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.177 as permitted sender)
client-ip=209.85.223.177; envelope-from=aaxiomfinity@gmail.com;
helo=mail-ie0-f177.google.com;
Received: from mail-ie0-f177.google.com ([209.85.223.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vtupo-00005g-1M
for bitcoin-development@lists.sourceforge.net;
Fri, 20 Dec 2013 07:49:26 +0000
Received: by mail-ie0-f177.google.com with SMTP id tp5so2566360ieb.8
for <bitcoin-development@lists.sourceforge.net>;
Thu, 19 Dec 2013 23:49:18 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.42.215.80 with SMTP id hd16mr4364673icb.17.1387525758791;
Thu, 19 Dec 2013 23:49:18 -0800 (PST)
Received: by 10.64.27.197 with HTTP; Thu, 19 Dec 2013 23:49:18 -0800 (PST)
Date: Thu, 19 Dec 2013 23:49:18 -0800
Message-ID: <CAE0e52VaUWDwEcXZfR7cRxyzQ90BPvv4K2JpuyELVYnWqAhi5w@mail.gmail.com>
From: Chris Evans <aaxiomfinity@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=20cf301d3cecf834e404edf28392
X-Spam-Score: -0.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
(aaxiomfinity[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Vtupo-00005g-1M
Subject: [Bitcoin-development] 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: Fri, 20 Dec 2013 07:49:26 -0000
--20cf301d3cecf834e404edf28392
Content-Type: text/plain; charset=ISO-8859-1
maybe make it so bitcoin.conf settings can be edited with in the app
instead of external editor, and make it easier to enable rpc server mode...
--20cf301d3cecf834e404edf28392
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">maybe make it so bitcoin.conf settings can be edited with =
in the app instead of external editor,=A0 and make it easier to enable rpc =
server mode...<br><br>=A0<br><br><br><br></div>
--20cf301d3cecf834e404edf28392--
|
