summaryrefslogtreecommitdiff
path: root/4f/3a1e86a274f7b32ec97242a9b5c45d29954a41
blob: fdceb8c991ae2a17524b700cc5350efd0bf50dcc (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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <grarpamp@gmail.com>) id 1SgX2B-0005l1-63
	for bitcoin-development@lists.sourceforge.net;
	Mon, 18 Jun 2012 08:10:03 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=grarpamp@gmail.com;
	helo=mail-wg0-f53.google.com; 
Received: from mail-wg0-f53.google.com ([74.125.82.53])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SgX2A-0000sh-FR
	for bitcoin-development@lists.sourceforge.net;
	Mon, 18 Jun 2012 08:10:03 +0000
Received: by wgbfm10 with SMTP id fm10so4419325wgb.10
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 18 Jun 2012 01:09:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.206.135 with SMTP id l7mr7482004weo.84.1340006996363; Mon,
	18 Jun 2012 01:09:56 -0700 (PDT)
Received: by 10.180.7.105 with HTTP; Mon, 18 Jun 2012 01:09:56 -0700 (PDT)
In-Reply-To: <201206180357.13430.luke@dashjr.org>
References: <CAD2Ti2_Z-mzHu_VG7fq+sgQj7CfdZ_nKoa7Q6nDObwBSL6yXgQ@mail.gmail.com>
	<201206180002.43785.luke@dashjr.org>
	<CAD2Ti28q2_c=AgUjapQQvLLoMcT4ay50q_PuYbwA3820747t1A@mail.gmail.com>
	<201206180357.13430.luke@dashjr.org>
Date: Mon, 18 Jun 2012 04:09:56 -0400
Message-ID: <CAD2Ti29_NcLyfEB3b=Xur=Q37SP6Cn34b5ZzOTmucLdni3of=w@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.3 (-)
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.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SgX2A-0000sh-FR
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 08:10:03 -0000

> Workflow is ...

Thanks very much, I think that helps me/others. I did not realize
there were release windows in master and thought it more as the
typical full time dev slush. That also explains the presence of all
the release tags in github repo. And even, in a divergent way, the
presence of github/0.6.2 as path to gitorius/0.6.x. And I agree
with the (last bugfix after release) -> import/maintain model, it
would be similar in solo repo.

> I guess I've been neglecting to update the stable repo with
> releases tagged in master. It should be fixed now.

Yes, that has helped! Now git'ers can easily compare the release
tags to stable 'x' branches on gitorious. I don't know how to do
that across repos yet, save manuel diff of checkouts from each,
which would have been required prior to this update you made.

Also, these declarations of defunctness help sort out too.

# git branch -vv -a
"This stable branch is no longer maintained."


Ok, so for my works I will now track github/master (edge) and
gitorious/0.bigN(eg: 6).x (stable) against gitorious/bigTagRelease
(latest public). Thanks guys, and Luke :)

I hope other with similar questions find this thread. Apology for
subverting its subject somehows.