blob: b0559474bb5dfa09f453dd4d45383842246485c1 (
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QbUyb-0007Ju-TF
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jun 2011 09:53:01 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=mh.in.england@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QbUyZ-0008HU-1h
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jun 2011 09:53:01 +0000
Received: by mail-vw0-f47.google.com with SMTP id 2so16836vws.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 28 Jun 2011 02:52:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.187.194 with SMTP id fu2mr9654689vdc.258.1309254778872;
Tue, 28 Jun 2011 02:52:58 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.169.40 with HTTP; Tue, 28 Jun 2011 02:52:58 -0700 (PDT)
In-Reply-To: <201106280257.22961.luke@dashjr.org>
References: <D024B465-AD6C-4AAD-A07F-956223929B6F@jrbobdobbs.org>
<C9421AA2-D741-4989-9DA8-395D1F532F52@jrbobdobbs.org>
<BANLkTi=RASna0vQ0bYGc8ApWC++PsNqSAg@mail.gmail.com>
<201106280257.22961.luke@dashjr.org>
Date: Tue, 28 Jun 2011 11:52:58 +0200
X-Google-Sender-Auth: u6xSq0b0sYLbej2raOfvlXrLLFo
Message-ID: <BANLkTimzHDW0Xkr52hNPt6TA21uLWE3JKtMnuLzE6QcM8MoefA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.3 (-)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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
0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QbUyZ-0008HU-1h
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: Live mtgox.com trade matching bug.
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: Tue, 28 Jun 2011 09:53:02 -0000
>> Could we keep the Mt Gox related stuff off bitcoin-development please?
>> It's not related to the core software.
>
> MtGox's code is just as related as BitcoinJ or any other Bitcoin software,
> IMO.
It's closed source, so nobody here can do anything about it (unlike
other software discussed here).
|
