public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Ok to use 0.8.x?
Date: Wed, 13 Mar 2013 22:49:36 -0400	[thread overview]
Message-ID: <CAD2Ti28XnZFDLMm+B1cxb5b+adjwk5M-DrFRs7C+VE=SLZ0hNQ@mail.gmail.com> (raw)

Assuming a new install and first time connection to the net,
is using 0.8.x [1] safe to use, for all (or select?) purposes,
regarding the current fork issue?

If not, is there a recommended branch, tag, or commit, for
all such (or select?) purposes, until such time as an upgrade
alert is broadcasted?

Thanks.

[1] Regarding possible 0.8.x flavors...

There are only 'branch master' and 'tag v0.8.0' here:
https://github.com/bitcoin/bitcoin

There are no 0.8.x branch or tags here yet:
https://git.gitorious.org/bitcoin/bitcoind-stable



             reply	other threads:[~2013-03-14  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14  2:49 grarpamp [this message]
2013-03-14  4:01 ` Gavin Andresen
2013-03-14  8:33   ` Michael Gronager
2013-03-16 22:04     ` grarpamp
2013-03-16 22:17       ` Peter Todd

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='CAD2Ti28XnZFDLMm+B1cxb5b+adjwk5M-DrFRs7C+VE=SLZ0hNQ@mail.gmail.com' \
    --to=grarpamp@gmail$(echo .)com \
    --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