public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: grarpamp <grarpamp@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
Date: Sun, 17 Jun 2012 17:52:18 -0400	[thread overview]
Message-ID: <CAAS2fgTHo0U+2U5vtbmTEiKB6rBHbfuRHsm-bcnRhSrs-2jZpw@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti29+=L+ss7fwivy+gfPFuE10sQdy68TGhL-30ngWKTLdQA@mail.gmail.com>

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.



  reply	other threads:[~2012-06-17 21:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17  9:22 grarpamp
2012-06-17 10:17 ` Gregory Maxwell
2012-06-17 21:35   ` grarpamp
2012-06-17 21:52     ` Gregory Maxwell [this message]
2012-06-17 23:04       ` grarpamp
2012-06-18  0:02         ` Luke-Jr
2012-06-18  3:27           ` grarpamp
2012-06-18  3:57             ` Luke-Jr
2012-06-18  8:09               ` grarpamp
2012-06-18 13:25                 ` Luke-Jr
2012-06-20  9:06                   ` grarpamp
2012-06-18  0:07         ` Gregory Maxwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAS2fgTHo0U+2U5vtbmTEiKB6rBHbfuRHsm-bcnRhSrs-2jZpw@mail.gmail.com \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=grarpamp@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox