From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD
Date: Tue, 20 Dec 2011 15:49:16 -0500 [thread overview]
Message-ID: <CABsx9T3u5onesvWr46ZnKCsYAnxxoLn38PuL6K7RrYqmX8pQHw@mail.gmail.com> (raw)
FYI for anybody who doesn't hang out in IRC:
I've been busy pulling patches into git HEAD for a Bitcoin version
0.6, with the goal of having a Release Candidate 1 out in a couple of
weeks.
So if you've done all your Christmas shopping and have time to help
test, code review, etc. now would be the time.
--
--
Gavin Andresen
next reply other threads:[~2011-12-20 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 20:49 Gavin Andresen [this message]
2011-12-21 1:46 ` [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD Luke-Jr
2011-12-21 10:12 ` Mike Hearn
2011-12-21 15:44 ` Luke-Jr
2011-12-21 16:45 ` Luke-Jr
2011-12-21 17:12 ` Jeff Garzik
2011-12-21 17:14 ` Luke-Jr
2011-12-21 17:17 ` Jeff Garzik
2011-12-21 17:37 ` Luke-Jr
2011-12-21 10:30 ` Wladimir
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=CABsx9T3u5onesvWr46ZnKCsYAnxxoLn38PuL6K7RrYqmX8pQHw@mail.gmail.com \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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