summaryrefslogtreecommitdiff
path: root/04/68b98e6526651a77bb530c8a8ebcf24204fbce
blob: b2e23b970eb00e3c658ea507f7ed6497f0a59378 (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
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <k.okupski@googlemail.com>) id 1X6cxf-0007oB-Qp
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jul 2014 09:54:19 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of googlemail.com
	designates 209.85.212.174 as permitted sender)
	client-ip=209.85.212.174; envelope-from=k.okupski@googlemail.com;
	helo=mail-wi0-f174.google.com; 
Received: from mail-wi0-f174.google.com ([209.85.212.174])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X6cxe-0005vY-WA
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jul 2014 09:54:19 +0000
Received: by mail-wi0-f174.google.com with SMTP id d1so2210185wiv.7
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 14 Jul 2014 02:54:09 -0700 (PDT)
X-Received: by 10.180.109.101 with SMTP id hr5mr23787900wib.25.1405331649557; 
	Mon, 14 Jul 2014 02:54:09 -0700 (PDT)
Received: from [192.168.1.65] (s53751712.adsl.online.nl. [83.117.23.18])
	by mx.google.com with ESMTPSA id
	eh10sm24528891wic.0.2014.07.14.02.54.08
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 14 Jul 2014 02:54:08 -0700 (PDT)
Message-ID: <53C3A8C0.5070608@googlemail.com>
Date: Mon, 14 Jul 2014 11:54:08 +0200
From: Krzysztof Okupski <k.okupski@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative;
	boundary="------------090302050102070406060500"
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
	(k.okupski[at]googlemail.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: 1X6cxe-0005vY-WA
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
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, 14 Jul 2014 09:54:20 -0000

This is a multi-part message in MIME format.
--------------090302050102070406060500
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dear all,

thank you for your invaluable feedback. As requested, the spec
will from now on be under version control. It can be found under:

https://github.com/minium/Bitcoin-Spec

The old link to the PDF will be, just in case, kept updated as well.


Warm greetings,
Krzysztof Okupski

--------------090302050102070406060500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear all,<br>
    <br>
    thank you for your invaluable feedback. As requested, the spec<br>
    will from now on be under version control. It can be found under:<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a class="moz-txt-link-freetext" href="https://github.com/minium/Bitcoin-Spec">https://github.com/minium/Bitcoin-Spec</a><br>
    <br>
    The old link to the PDF will be, just in case, kept updated as well.<br>
    <br>
    <br>
    Warm greetings,<br>
    Krzysztof Okupski<br>
  </body>
</html>

--------------090302050102070406060500--