blob: 1cecf91781f3c9ba95017ab5e48c01cca516b854 (
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WmSUB-0005GQ-OF
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 18:40:31 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.44 as permitted sender)
client-ip=209.85.219.44; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f44.google.com;
Received: from mail-oa0-f44.google.com ([209.85.219.44])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WmSUA-0002UT-Tm
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 18:40:31 +0000
Received: by mail-oa0-f44.google.com with SMTP id o6so6705515oag.3
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 May 2014 11:40:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.115.199 with SMTP id jq7mr5916682obb.70.1400524825485;
Mon, 19 May 2014 11:40:25 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Mon, 19 May 2014 11:40:25 -0700 (PDT)
In-Reply-To: <c4d00173-a233-4f55-988a-ad2ba771d457@email.android.com>
References: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
<5377892C.8080402@gmail.com>
<CAAS2fgS-Ewj3T0-d=h7ET9dCz3+NPPYVOLDWd7T7oYY95x-sUA@mail.gmail.com>
<CALDj+Bbsb6JiLabTBx21k02dDvnmZZDCXmJ2mnh7DngBon202w@mail.gmail.com>
<5379FF38.4050909@certimix.com>
<20140519144709.GA29574@netbook.cypherspace.org>
<CANEZrP3sDh3Q9T0xFi7maNQR9Z6R7gQ6vT5kjchcMkD0hMHOdw@mail.gmail.com>
<c4d00173-a233-4f55-988a-ad2ba771d457@email.android.com>
Date: Mon, 19 May 2014 20:40:25 +0200
X-Google-Sender-Auth: bEiMrijoUpaX2hkEVmn98Spld9M
Message-ID: <CANEZrP047f0=9Bt8qEc2MLeOBay4sQXAR9zpL1rKKzSsmk2oaA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=047d7b678120b8e89104f9c5180f
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 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
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WmSUA-0002UT-Tm
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] patents...
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, 19 May 2014 18:40:31 -0000
--047d7b678120b8e89104f9c5180f
Content-Type: text/plain; charset=UTF-8
>
> Meh. The world is much bigger than the USA. Secondly that rule makes it
> difficult to educate people about why patents are as bad as they are.
>
You can easily find examples that are not relevant to Bitcoin if you want
to discuss the patent system in general.
> Feel free to continue censoring your own discussion within closed
> corporate environments. But to say keeping patent discussion off mailing
> lists is appropriate or wise when the tech news is full of such discussion
> is silly.
It is both appropriate and wise. Please keep discussion of Bitcoin-relevant
patents elsewhere.
--047d7b678120b8e89104f9c5180f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"">Meh. The world is much bigger th=
an the USA. Secondly that rule makes it difficult to educate people about w=
hy patents are as bad as they are.<br>
</div></blockquote><div><br></div><div>You can easily find examples that ar=
e not relevant to Bitcoin if you want to discuss the patent system in gener=
al.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D""></div>
Feel free to continue censoring your own discussion within closed corporate=
environments. But to say keeping patent discussion off mailing lists is ap=
propriate or wise when the tech news is full of such discussion is silly.</=
blockquote>
<div><br></div><div>It is both appropriate and wise. Please keep discussion=
of Bitcoin-relevant patents elsewhere.</div></div></div></div>
--047d7b678120b8e89104f9c5180f--
|
