summaryrefslogtreecommitdiff
path: root/f7/d505ba69d82526214032f8189b25f3b8fb64eb
blob: d44ba7ab7350f0767c43ab27e1bcead6b1d6a456 (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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <drak@zikula.org>) id 1WCu3J-0007i1-Ae
	for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Feb 2014 16:49:49 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of zikula.org
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=drak@zikula.org;
	helo=mail-wg0-f53.google.com; 
Received: from mail-wg0-f53.google.com ([74.125.82.53])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WCu3I-0005ik-3N
	for bitcoin-development@lists.sourceforge.net;
	Mon, 10 Feb 2014 16:49:49 +0000
Received: by mail-wg0-f53.google.com with SMTP id y10so4314823wgg.8
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 10 Feb 2014 08:49:42 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type;
	bh=wGVR24biZ8WDGwH+Ny7HQ/nUDkOD/L0pkXAy3I/Ja6s=;
	b=lbrDIWCN3wYzs5H6bW6XnOOQNXvEZ3XLugNfUEChBdu3nmQBiK2K3Lz66SEpJS/IUc
	TtcdIZDrdcSO8STyX2xIwMCdKA5oqG5EEkLXMSzo3dd0NLtNvL62W3ks3Pmbkg2EQIc2
	l/CS6iZNqtzmyteW8YerYD5w0Kp3n7mvTaC9k4dbY4S+y9JOgGT9iLkykhWl/wSpSOVF
	rEFnj1smKlvb2d79Keh4Xre99IosaSeyglJUMxebB1+kMR6XYNkk+xoA9txplzJvQNRO
	T1AinLy/hPnIZ/LiV2HZyvlnkY+ZXqkQNRKoJVsUKvMze4R/eHzHfu/eo6NyL8kz9FRi
	5jFg==
X-Gm-Message-State: ALoCoQlbGp3bTtO16Adccm0wbucU1DN0xzSvd1NKSfm1+SlS23w8fVM0LwO/53xn5Jm5ryqgc1sz
X-Received: by 10.180.185.197 with SMTP id fe5mr11144145wic.56.1392050981909; 
	Mon, 10 Feb 2014 08:49:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.205.69 with HTTP; Mon, 10 Feb 2014 08:49:21 -0800 (PST)
In-Reply-To: <20140210144003.2BDCCDDAEFC@quidecco.de>
References: <CANAnSg1LgpHGf-vTV0to1Z7sogf1ic6WTbogEsrQy1wh4C5zfw@mail.gmail.com>
	<20140210144003.2BDCCDDAEFC@quidecco.de>
From: Drak <drak@zikula.org>
Date: Mon, 10 Feb 2014 16:49:21 +0000
Message-ID: <CANAnSg0OUuETUhbQYoXHf12yxBHsZ_czBwxbtD8Btg9E+cJTOg@mail.gmail.com>
To: Isidor Zeuner <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c34e9e494ed504f21020f6
X-Spam-Score: -0.5 (/)
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_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1WCu3I-0005ik-3N
Subject: Re: [Bitcoin-development] MtGox blames bitcoin
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, 10 Feb 2014 16:49:49 -0000

--001a11c34e9e494ed504f21020f6
Content-Type: text/plain; charset=UTF-8

Well done Gavin for quickly setting the record straight[1] officially as
project lead. MtGox tried to blame their issues by throwing Bitcoin under a
bus and I am glad there has been a public rebuttal showing up their
incompetence which is doing harm to the bitcoin eco system. Basically, yes
there are issues, but MtGox should have worked around it.

Also thanks to Gregory for also writing[2] about the matter.

Drak

[1] https://bitcoinfoundation.org/blog/?p=418
[2]
http://www.cryptocoinsnews.com/2014/02/10/mt-gox-blames-bitcoin-core-developer-greg-maxwell-responds/

--001a11c34e9e494ed504f21020f6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Well done Gavin for quickly setting the record straight[1]=
 officially as project lead. MtGox tried to blame their issues by throwing =
Bitcoin under a bus and I am glad there has been a public rebuttal showing =
up their incompetence which is doing harm to the bitcoin eco system. Basica=
lly, yes there are issues, but MtGox should have worked around it.<div>

<br></div><div>Also thanks to Gregory for also writing[2] about the matter.=
</div><div><br></div><div>Drak<br></div><div><div><br></div><div>[1]=C2=A0<=
a href=3D"https://bitcoinfoundation.org/blog/?p=3D418">https://bitcoinfound=
ation.org/blog/?p=3D418</a></div>

<div>[2]=C2=A0<a href=3D"http://www.cryptocoinsnews.com/2014/02/10/mt-gox-b=
lames-bitcoin-core-developer-greg-maxwell-responds/">http://www.cryptocoins=
news.com/2014/02/10/mt-gox-blames-bitcoin-core-developer-greg-maxwell-respo=
nds/</a></div>

<div><br></div></div></div>

--001a11c34e9e494ed504f21020f6--