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
118
119
120
121
122
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1SgSdD-0001S4-Tm
for bitcoin-development@lists.sourceforge.net;
Mon, 18 Jun 2012 03:27:59 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com;
helo=mail-we0-f175.google.com;
Received: from mail-we0-f175.google.com ([74.125.82.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SgSdD-0001Dq-74
for bitcoin-development@lists.sourceforge.net;
Mon, 18 Jun 2012 03:27:59 +0000
Received: by werg55 with SMTP id g55so3801934wer.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 17 Jun 2012 20:27:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.207.27 with SMTP id m27mr6990969weo.42.1339990072991; Sun,
17 Jun 2012 20:27:52 -0700 (PDT)
Received: by 10.180.7.105 with HTTP; Sun, 17 Jun 2012 20:27:52 -0700 (PDT)
In-Reply-To: <201206180002.43785.luke@dashjr.org>
References: <CAD2Ti2_Z-mzHu_VG7fq+sgQj7CfdZ_nKoa7Q6nDObwBSL6yXgQ@mail.gmail.com>
<CAAS2fgTHo0U+2U5vtbmTEiKB6rBHbfuRHsm-bcnRhSrs-2jZpw@mail.gmail.com>
<CAD2Ti28eC6A2+k8JfV3nXMLmye12K28rfCAorby87aXgV2ZGaQ@mail.gmail.com>
<201206180002.43785.luke@dashjr.org>
Date: Sun, 17 Jun 2012 23:27:52 -0400
Message-ID: <CAD2Ti28q2_c=AgUjapQQvLLoMcT4ay50q_PuYbwA3820747t1A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.2 (-)
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.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SgSdD-0001Dq-74
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
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: Mon, 18 Jun 2012 03:28:00 -0000
> be sure to have good backups that never touched the new code...
> We have at various times had bugs in master that would corrupt
> wallets
Sorry, that's to be expected, I shouldn't have asked.
> It would be very helpful if anyone offering bitcoin services would
> setup parallel toy versions of your sites on testnet...
Good point.
> we don't currently have enough testing activity on master.
I usually test compile / report current and stable of things I use.
So I get that github/master is the obvious top of things.
But in looking at where the tags are between repositories,
it's still not clear to me what the workflow is.
Example...
There are these release tarballs on sourceforge, which all have
tags in github, yet no tags in gitorious. There are no 'x' branches
on github, yet there is one release applicable branch on gitorious.
I guess I'd expect to see, that if as hinted by Luke that gitorious
has the stable trees, that there would be release tags there, laid
down at some comfy point in time on the 'x' stable branches there.
(The stable branches inheriting new code from master). But there
are no such tags.
And the releases/tags seem to magically appear from nowhere on
github :) Again, I'm trying to extricate myself from CVS here.
# sourceforge tarballs
0.6.0
0.6.1
0.6.2
0.6.2.2
# github branches
remotes/origin/master 432d28d Merge pull request #1477 from
gmaxwell/master
remotes/origin/0.6.2 40fd689 Bump version to 0.6.2.2 for
osx-special build
# github tags
v0.6.0
v0.6.1
v0.6.2
v0.6.2.1
v0.6.2.2
# gitorius branches
remotes/origin/0.6.0.x d354f94 Merge branch '0.5.x' into 0.6.0.x
remotes/origin/0.6.x 5e322a7 Merge branch '0.6.0.x' into 0.6.x
# gitorious tags
v0.6.0.7
|
