summaryrefslogtreecommitdiff
path: root/15/11087eb5513c702a5aa174bb20fe4f55c77db1
blob: b80442d194ff4d4a615d999de11ff78cf159d149 (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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <rmckay@gmail.com>) id 1QiGqg-0000Nl-HV
	for bitcoin-development@lists.sourceforge.net;
	Sun, 17 Jul 2011 02:12:50 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.47 as permitted sender)
	client-ip=209.85.212.47; envelope-from=rmckay@gmail.com;
	helo=mail-vw0-f47.google.com; 
Received: from mail-vw0-f47.google.com ([209.85.212.47])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1QiGqe-0006Uu-W8
	for bitcoin-development@lists.sourceforge.net;
	Sun, 17 Jul 2011 02:12:50 +0000
Received: by vws2 with SMTP id 2so2373223vws.34
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 16 Jul 2011 19:12:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.177.101 with SMTP id cp5mr5064359vdc.343.1310868762285;
	Sat, 16 Jul 2011 19:12:42 -0700 (PDT)
Sender: rmckay@gmail.com
Received: by 10.52.184.202 with HTTP; Sat, 16 Jul 2011 19:12:42 -0700 (PDT)
In-Reply-To: <CA+8xBpf-xrmz3Eo7ZjitUHivR1fU4gRZt_1mdi=1EDrOLpZmVw@mail.gmail.com>
References: <CAJNQ0stPb+3yarKh4M+tFpjSaSG4-GrZX9AVFPh5q7+Ho_OJOA@mail.gmail.com>
	<1310813679.2195.0.camel@Desktop666>
	<CAJNQ0st1hv4k-11EHOPDqkkXCGQh41ysKhUmT6qgLu8uaGng=Q@mail.gmail.com>
	<CAJNQ0svFL6JMpcRNyJ=xpv0wrn1EpGOUG7ff2-JXH5BKJVHZqQ@mail.gmail.com>
	<CA+8xBpduc=vn_Q7Kw0m+VkuHjz0FTxjDZB+hOPLnRJcuh49gJw@mail.gmail.com>
	<83816D44-004A-43C4-AFFE-ED1BABD90144@jrbobdobbs.org>
	<CA+8xBpf-xrmz3Eo7ZjitUHivR1fU4gRZt_1mdi=1EDrOLpZmVw@mail.gmail.com>
Date: Sun, 17 Jul 2011 03:12:42 +0100
X-Google-Sender-Auth: RRy1ww3GvBY8d7gnEEBr2wXHGSE
Message-ID: <CAAqW1RE9MfUFb4quwtvX+BNhx7ream6yiSQGuQt1KSPMXyipUQ@mail.gmail.com>
From: Robert McKay <robert@mckay.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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
	(rmckay[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
X-Headers-End: 1QiGqe-0006Uu-W8
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] The forums...
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: Sun, 17 Jul 2011 02:12:50 -0000

On 7/17/11, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Sat, Jul 16, 2011 at 9:16 PM, Douglas Huff <dhuff@jrbobdobbs.org> wrote:
>> I say just kill the forum.bitcoin.org DNS entry along with it.
>
> Hopefully sirius will do this when he moves forum.bitcoin.org to
> forum.bitcointalk.org.
>
> But sirius is the only one with keys to bitcoin.org DNS, so....

At the risk of making myself very unpopular, perhaps it's the
development project that should move to a new URL?

Rob