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
74
75
76
77
78
79
80
81
82
83
|
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 <laanwj@gmail.com>) id 1WjjW4-00076H-HD
for bitcoin-development@lists.sourceforge.net;
Mon, 12 May 2014 06:15:12 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.178 as permitted sender)
client-ip=209.85.213.178; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f178.google.com;
Received: from mail-ig0-f178.google.com ([209.85.213.178])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WjjW2-0003re-DU
for bitcoin-development@lists.sourceforge.net;
Mon, 12 May 2014 06:15:11 +0000
Received: by mail-ig0-f178.google.com with SMTP id hl10so3431557igb.5
for <bitcoin-development@lists.sourceforge.net>;
Sun, 11 May 2014 23:15:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.111.138 with SMTP id ii10mr39455166igb.34.1399875304501;
Sun, 11 May 2014 23:15:04 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Sun, 11 May 2014 23:15:04 -0700 (PDT)
In-Reply-To: <536EDBA5.2010700@gmail.com>
References: <536EDBA5.2010700@gmail.com>
Date: Mon, 12 May 2014 08:15:04 +0200
Message-ID: <CA+s+GJBpkuBroz3AAcMCvKwEgwCbuqHJUUtVoQjWiGK9kniiGw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: =?UTF-8?Q?Sa=C3=AFvann_Carignan?= <saivann@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1WjjW2-0003re-DU
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Developer documentation on bitcoin.org
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: Mon, 12 May 2014 06:15:12 -0000
On Sun, May 11, 2014 at 4:08 AM, Sa=C3=AFvann Carignan <saivann@gmail.com> =
wrote:
> A new "Developer Documentation" section should be soon merged on
> bitcoin.org .
>
> Live Preview:
> http://bitcoindev.us.to/en/developer-documentation
>
> GitHub Pull Request:
> https://github.com/bitcoin/bitcoin.org/pull/393
>
> Bitcointalk Thread:
> https://bitcointalk.org/index.php?topic=3D511876.0
Great work!
Very nice to see thorough developer documentation on bitcoin.org.
I've already been reading it now and then and haven't found any
technical issues yet, if I do, I'll let you know.
Wladimir
|
