From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Cc: Matt Corallo <matt@bluematt.me>
Subject: [Bitcoin-development] Ready for 0.3.23 release?
Date: Mon, 13 Jun 2011 16:44:11 -0400 [thread overview]
Message-ID: <BANLkTikipPm9QU5NRnsKhfN6iF-Ua6duBg@mail.gmail.com> (raw)
(cc'd the devs that I'm not sure are on the dev mailing list yet)
Version 0.3.23 doesn't seem to have major issues, and testing has been
unremarkable. I think we can go ahead and push it out.
ACK for final release of 0.3.23?
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
reply other threads:[~2011-06-13 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BANLkTikipPm9QU5NRnsKhfN6iF-Ua6duBg@mail.gmail.com \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=matt@bluematt.me \
/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