public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
Date: Mon, 18 Jun 2012 00:02:41 +0000	[thread overview]
Message-ID: <201206180002.43785.luke@dashjr.org> (raw)
In-Reply-To: <CAD2Ti28eC6A2+k8JfV3nXMLmye12K28rfCAorby87aXgV2ZGaQ@mail.gmail.com>

On Sunday, June 17, 2012 11:04:42 PM grarpamp wrote:
> >> 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.
> 
> Ah ok, coming from cvs/svn, it's a bit different to find things.
> There's something to be said for maintenance of pior branches.
> Though I see some things I can use in github and my work would
> be more useful there, so maybe I'll stwitch to that from gitorius/0.6.x.
> 
> Presumably the github/0.6.2 branch is safe for production?

No, that was a temporary branch of what became the stable 0.6.x branch.
GitHub/master is bleeding edge. For production, you usually want the stable 
branches/releases (which are on Gitorious).

The fix to -detachdb's position in -help was just merged to master, and should 
be backported sometime in the next few days.

Luke



  reply	other threads:[~2012-06-18  0:03 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
2012-06-17 23:04       ` grarpamp
2012-06-18  0:02         ` Luke-Jr [this message]
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=201206180002.43785.luke@dashjr.org \
    --to=luke@dashjr$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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