From: Jeff Garzik <jgarzik@exmulti.com>
To: Arklan Uth Oslin <arklan.uthoslin@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.7.1 release candidate 1 ready for testing
Date: Thu, 11 Oct 2012 15:20:16 -0400 [thread overview]
Message-ID: <CA+8xBpedKZ6SYn-+O-uZQZcreHd-Yt_N-sR6CB4XUOgDU9vr-w@mail.gmail.com> (raw)
In-Reply-To: <CAGg41SWrgCKjAZH3LCGkt5juDg97wNR=VogzD59snF9yPHw2sQ@mail.gmail.com>
On Thu, Oct 11, 2012 at 1:51 PM, Arklan Uth Oslin
<arklan.uthoslin@gmail.com> wrote:
> i'll second the bitcoin test list.
As you like, but... bitcoin-devel is quite low traffic, so there is
not exactly an issue of crowding. And a separate list means people
cannot chime in as easily.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next prev parent reply other threads:[~2012-10-11 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:46 [Bitcoin-development] 0.7.1 release candidate 1 ready for testing Gavin Andresen
2012-10-11 15:59 ` Jeff Garzik
2012-10-11 16:17 ` Arklan Uth Oslin
2012-10-11 17:45 ` steve
2012-10-11 17:51 ` Arklan Uth Oslin
2012-10-11 19:20 ` Jeff Garzik [this message]
2012-10-11 20:08 ` Arklan Uth Oslin
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=CA+8xBpedKZ6SYn-+O-uZQZcreHd-Yt_N-sR6CB4XUOgDU9vr-w@mail.gmail.com \
--to=jgarzik@exmulti.com \
--cc=arklan.uthoslin@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