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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1RzEo1-00088A-Pz
for bitcoin-development@lists.sourceforge.net;
Sun, 19 Feb 2012 22:00:29 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=grarpamp@gmail.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RzEo0-0002zE-NR
for bitcoin-development@lists.sourceforge.net;
Sun, 19 Feb 2012 22:00:29 +0000
Received: by wibhq7 with SMTP id hq7so3502457wib.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 19 Feb 2012 14:00:22 -0800 (PST)
Received-SPF: pass (google.com: domain of grarpamp@gmail.com designates
10.180.78.98 as permitted sender) client-ip=10.180.78.98;
Authentication-Results: mr.google.com;
spf=pass (google.com: domain of grarpamp@gmail.com
designates 10.180.78.98 as permitted sender)
smtp.mail=grarpamp@gmail.com;
dkim=pass header.i=grarpamp@gmail.com
Received: from mr.google.com ([10.180.78.98])
by 10.180.78.98 with SMTP id a2mr12244335wix.17.1329688822635 (num_hops
= 1); Sun, 19 Feb 2012 14:00:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.78.98 with SMTP id a2mr10255120wix.17.1329688822569; Sun,
19 Feb 2012 14:00:22 -0800 (PST)
Received: by 10.180.103.132 with HTTP; Sun, 19 Feb 2012 14:00:22 -0800 (PST)
Date: Sun, 19 Feb 2012 17:00:22 -0500
Message-ID: <CAD2Ti2-0nMARZ-vyDk0-ToKF-SvHMrG65Pe9Bwv6TLkfwmEqew@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.4 (-)
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
(grarpamp[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
0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RzEo0-0002zE-NR
Subject: [Bitcoin-development] Git repo choices
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, 19 Feb 2012 22:00:29 -0000
I'm a little unclear on which repo is which and
for what intended uses. And other than #1,
their descriptions on the hubs are minimal.
I'm not the best with git, but getting there.
Are these the right way to think of them?
And that #1 and #3 are what most builders
and hacks should be tracking?
#1
https://github.com/bitcoin/bitcoin.git
The current development tree. As such, HEAD/master/origin
may at times not be exactly reliable/usable.
#2
https://git.gitorious.org/bitcoin/bitcoind.git
A copy of some chunk of #1 that then died
off around v0.4.0. Purposed similar to #3?
#3
https://git.gitorious.org/bitcoin/bitcoind-stable.git
Another copy of #1. For development along stable
branches and making release cuts from same?
Releases get pulled back to #1 for keeping?
The HEAD/master/origin should be reliable.
Why is this functoin not a part of #1?
Thanks.
|
