From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.8.2 branch
Date: Thu, 30 May 2013 02:57:06 +0000 [thread overview]
Message-ID: <201305300257.09231.luke@dashjr.org> (raw)
In-Reply-To: <CAD2Ti2_pp3jgsq3s93NGdLi-Ojtyu11DTu9aoqy657DteqSdUg@mail.gmail.com>
On Thursday, May 30, 2013 2:54:00 AM grarpamp wrote:
> Should there not be a 0.8.2 branch laid down at 09e437b (v0.8.2)
> in which the like of release build stoppers or critfixes such as d315eb0
> are included... for those tracking that level of defect without
> wishing to track all the growing post release slush in HEAD?
I'll branch 0.8.x sometime in the next few weeks.
Stable branches are maintained on Gitorious for now:
http://gitorious.org/bitcoin/bitcoind
Luke
prev parent reply other threads:[~2013-05-30 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 2:54 grarpamp
2013-05-30 2:57 ` Luke-Jr [this message]
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=201305300257.09231.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