summaryrefslogtreecommitdiff
path: root/db/115920a2e23d764b55849076b67920551a98d0
blob: b050e9c11c60873839625c8f537333870e6d79c3 (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
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 <gavinandresen@gmail.com>) id 1S2SDx-0008HW-KF
	for bitcoin-development@lists.sourceforge.net;
	Tue, 28 Feb 2012 18:56:33 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.41 as permitted sender)
	client-ip=74.125.82.41; envelope-from=gavinandresen@gmail.com;
	helo=mail-ww0-f41.google.com; 
Received: from mail-ww0-f41.google.com ([74.125.82.41])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1S2SDw-0002pL-UL
	for bitcoin-development@lists.sourceforge.net;
	Tue, 28 Feb 2012 18:56:33 +0000
Received: by wgbds1 with SMTP id ds1so2144207wgb.4
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 28 Feb 2012 10:56:26 -0800 (PST)
Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates
	10.180.24.68 as permitted sender) client-ip=10.180.24.68; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of
	gavinandresen@gmail.com designates 10.180.24.68 as permitted
	sender) smtp.mail=gavinandresen@gmail.com;
	dkim=pass header.i=gavinandresen@gmail.com
Received: from mr.google.com ([10.180.24.68])
	by 10.180.24.68 with SMTP id s4mr5031212wif.22.1330455386889 (num_hops
	= 1); Tue, 28 Feb 2012 10:56:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.24.68 with SMTP id s4mr4058233wif.22.1330455386820; Tue,
	28 Feb 2012 10:56:26 -0800 (PST)
Received: by 10.223.121.197 with HTTP; Tue, 28 Feb 2012 10:56:26 -0800 (PST)
Date: Tue, 28 Feb 2012 13:56:26 -0500
Message-ID: <CABsx9T3t_=BWJ0PvTLTS=oGxVYA1vRTD3t3Wo5D1=jfO6HG-7g@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=f46d043894c1b890b804ba0ac87f
X-Spam-Score: -0.8 (/)
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.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1S2SDw-0002pL-UL
Subject: [Bitcoin-development] Anything to chat about today at 21:00 UTC ?
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 Feb 2012 18:56:33 -0000

--f46d043894c1b890b804ba0ac87f
Content-Type: text/plain; charset=ISO-8859-1

I'll be in the #bitcoin-development IRC channel in two hours, for the
semi-regular Tuesday IRC meeting. Things that might be worth some
discussion:

+ The duplicate coinbase attack/fix, and strategy for rolling out sipa's
fix.

+ 0.6 release schedule

+ Is there anything we can do to attract a great Windows developer?  (we've
got issues piling up...)

+ Multisignature next-steps: who is working on what?

Am I forgetting anything?

-- 
--
Gavin Andresen

--f46d043894c1b890b804ba0ac87f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;ll be in the #bitcoin-development IRC channel in two hours, for the s=
emi-regular Tuesday IRC meeting. Things that might be worth some discussion=
:<div><br></div><div>+ The duplicate coinbase attack/fix, and strategy for =
rolling out sipa&#39;s fix.</div>
<div><br></div><div>+ 0.6 release schedule<br><br>+ Is there anything we ca=
n do to attract a great Windows developer? =A0(we&#39;ve got issues piling =
up...)<br><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">+=
 Multisignature next-steps: who is working on what?</div>
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Am I forget=
ting anything?</div><div class=3D"gmail_quote"><br></div>-- <br>--<br>Gavin=
 Andresen<br><br>
</div>

--f46d043894c1b890b804ba0ac87f--