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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kanzure@gmail.com>) id 1XJlao-0000l1-Gm
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Aug 2014 15:45:02 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.51 as permitted sender)
client-ip=209.85.219.51; envelope-from=kanzure@gmail.com;
helo=mail-oa0-f51.google.com;
Received: from mail-oa0-f51.google.com ([209.85.219.51])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XJlan-0003lP-1g
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Aug 2014 15:45:01 +0000
Received: by mail-oa0-f51.google.com with SMTP id o6so5317654oag.38
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Aug 2014 08:44:55 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.94.230 with SMTP id df6mr44334510obb.36.1408463095566;
Tue, 19 Aug 2014 08:44:55 -0700 (PDT)
Received: by 10.60.70.33 with HTTP; Tue, 19 Aug 2014 08:44:55 -0700 (PDT)
In-Reply-To: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com>
References: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com>
Date: Tue, 19 Aug 2014 10:44:55 -0500
Message-ID: <CABaSBayBsHsVO=Wan3C-H4s9b=xJixRMk+O=+id0CH_0B_Nbmw@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>, Bryan Bishop <kanzure@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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
(kanzure[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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
X-Headers-End: 1XJlan-0003lP-1g
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Reconsidering github
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, 19 Aug 2014 15:45:02 -0000
On Tue, Aug 19, 2014 at 7:02 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> As a first step, one possibility is putting the primary repo on
> bitcoin.org somewhere, and simply mirroring that to github for each
> push.
Smaller first step would be to mirror the git repository on
bitcoin.org, which is necessary anyway before switching primaries.
- Bryan
http://heybryan.org/
1 512 203 0507
|