From mboxrd@z Thu Jan  1 00:00:00 1970
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 <gmaxwell@gmail.com>) id 1SgNOT-0000IB-9n
	for bitcoin-development@lists.sourceforge.net;
	Sun, 17 Jun 2012 21:52:25 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.175 as permitted sender)
	client-ip=209.85.216.175; envelope-from=gmaxwell@gmail.com;
	helo=mail-qc0-f175.google.com; 
Received: from mail-qc0-f175.google.com ([209.85.216.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1SgNOS-0001hS-9p
	for bitcoin-development@lists.sourceforge.net;
	Sun, 17 Jun 2012 21:52:25 +0000
Received: by qcso7 with SMTP id o7so2625248qcs.34
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 17 Jun 2012 14:52:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.210.198 with SMTP id gl6mr23704116qab.7.1339969938808;
	Sun, 17 Jun 2012 14:52:18 -0700 (PDT)
Received: by 10.229.144.205 with HTTP; Sun, 17 Jun 2012 14:52:18 -0700 (PDT)
In-Reply-To: <CAD2Ti29+=L+ss7fwivy+gfPFuE10sQdy68TGhL-30ngWKTLdQA@mail.gmail.com>
References: <CAD2Ti2_Z-mzHu_VG7fq+sgQj7CfdZ_nKoa7Q6nDObwBSL6yXgQ@mail.gmail.com>
	<CAAS2fgQCc_-FgiXs0JABkAzZWNrbhhWYutvRgFLsnKYaEWDqwQ@mail.gmail.com>
	<CAD2Ti29+=L+ss7fwivy+gfPFuE10sQdy68TGhL-30ngWKTLdQA@mail.gmail.com>
Date: Sun, 17 Jun 2012 17:52:18 -0400
Message-ID: <CAAS2fgTHo0U+2U5vtbmTEiKB6rBHbfuRHsm-bcnRhSrs-2jZpw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: grarpamp <grarpamp@gmail.com>
Content-Type: text/plain; charset=UTF-8
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
	(gmaxwell[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.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SgNOS-0001hS-9p
Cc: bitcoin-development@lists.sourceforge.net
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: Sun, 17 Jun 2012 21:52:25 -0000

On Sun, Jun 17, 2012 at 5:35 PM, grarpamp <grarpamp@gmail.com> wrote:
>> It isn't inside the ifdef in bitcoin git master.
>
> Oh, hmm, well then, what is the difference or usage
> between these two repositories in regards to the project?
> Which one are the formal releases tagged (tbz's cut) in?
>
> Which one has the branches with the commits that will
> make it into the next formal release? ie: tracking along
> 0.5.x, 0.6.x, HEAD/master (to be branched for 0.7.x).
>
> https://github.com/bitcoin/bitcoin
> https://git.gitorious.org/bitcoin/bitcoind-stable

The latter is Luke's backports of security and stability fixes to
otherwise unmaintained old versions.