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
114
115
116
117
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1S0FIf-0007Mr-73
for bitcoin-development@lists.sourceforge.net;
Wed, 22 Feb 2012 16:44:17 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=gavinandresen@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-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 1S0FIb-0005mt-5y
for bitcoin-development@lists.sourceforge.net;
Wed, 22 Feb 2012 16:44:17 +0000
Received: by wgbdr12 with SMTP id dr12so212168wgb.10
for <bitcoin-development@lists.sourceforge.net>;
Wed, 22 Feb 2012 08:44:07 -0800 (PST)
Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates
10.180.83.70 as permitted sender) client-ip=10.180.83.70;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of
gavinandresen@gmail.com designates 10.180.83.70 as permitted
sender) smtp.mail=gavinandresen@gmail.com;
dkim=pass header.i=gavinandresen@gmail.com
Received: from mr.google.com ([10.180.83.70])
by 10.180.83.70 with SMTP id o6mr37752693wiy.19.1329929047041 (num_hops
= 1); Wed, 22 Feb 2012 08:44:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.83.70 with SMTP id o6mr31342541wiy.19.1329929047002; Wed,
22 Feb 2012 08:44:07 -0800 (PST)
Received: by 10.223.116.15 with HTTP; Wed, 22 Feb 2012 08:44:06 -0800 (PST)
Date: Wed, 22 Feb 2012 11:44:06 -0500
Message-ID: <CABsx9T1X4Na==_dYC0Zb0=WcLQQTQ6cnaKf92UTEw4iGxOO_TA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: =?ISO-8859-1?Q?Michael_Gr=F8nager?= <gronager@ceptacle.com>
Content-Type: multipart/alternative; boundary=f46d044288546c4ce804b9903c03
X-Spam-Score: -0.9 (/)
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
(gavinandresen[at]gmail.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
-0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1S0FIb-0005mt-5y
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Where to have discussions...
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: Wed, 22 Feb 2012 16:44:17 -0000
--f46d044288546c4ce804b9903c03
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Wed, Feb 22, 2012 at 11:29 AM, Michael Gr=F8nager <gronager@ceptacle.com=
>wrote:
> PS: I have said so before, but it would *really* be nice if discussions /
> conclusions / irc-summaries were taking place at one place - e.g. at the
> bitcoin-dev mailing list, not at 5-10 different threads in bitcointalk or
> in bip notes or solely on IRC...
I've been trying to move discussions to this mailing list, by starting
conversations here and posting links to the mailing list archives in the
discussion forums just so people know there is a conversation going on.
IRC conversations are great for rapid back-and-forth brainstorming, so I
expect a lot of work to continue getting done via IRC, but once there's
general consensus there I expect issues to migrate here.
--=20
--
Gavin Andresen
--f46d044288546c4ce804b9903c03
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">On Wed, Feb 22, 2012 at 11:29 AM, Michael Gr=F8n=
ager <span dir=3D"ltr"><<a href=3D"mailto:gronager@ceptacle.com">gronage=
r@ceptacle.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
PS: I have said so before, but it would *really* be nice if discussions / c=
onclusions / irc-summaries were taking place at one place - e.g. at the bit=
coin-dev mailing list, not at 5-10 different threads in bitcointalk or in b=
ip notes or solely on IRC...</blockquote>
<div><br></div><div>I've been trying to move discussions to this mailin=
g list, by starting conversations here and posting links to the mailing lis=
t archives in the discussion forums just so people know there is a conversa=
tion going on.</div>
<div><br></div><div>IRC conversations are great for rapid back-and-forth br=
ainstorming, so I expect a lot of work to continue getting done via IRC, bu=
t once there's general consensus there I expect issues to migrate here.=
</div>
</div><div><br></div>-- <br>--<br>Gavin Andresen<br><br>
--f46d044288546c4ce804b9903c03--
|
