From: "Luke-Jr" <luke@dashjr.org>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.4.x stable branch
Date: Tue, 20 Sep 2011 16:37:50 -0400 [thread overview]
Message-ID: <201109201637.52006.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpd9wBGLBnfXr=OiLYxVPvxegoi+eMqHFqpQRoaVW1uvKw@mail.gmail.com>
On Tuesday, September 20, 2011 3:10:16 PM Jeff Garzik wrote:
> Thus, we observe a few things that may be applied to bitcoin:
This is basically what the #bitcoin-stable team wants to do.
next prev parent reply other threads:[~2011-09-20 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 23:30 [Bitcoin-development] 0.4.x stable branch Luke-Jr
2011-09-19 12:49 ` Gavin Andresen
2011-09-19 13:03 ` Gregory Maxwell
2011-09-19 13:48 ` Amir Taaki
2011-09-19 15:00 ` Luke-Jr
2011-09-19 15:06 ` Gregory Maxwell
2011-09-20 4:41 ` theymos
2011-09-20 19:10 ` Jeff Garzik
2011-09-20 20:37 ` Luke-Jr [this message]
2011-09-21 14:24 ` Alex Waters
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=201109201637.52006.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@exmulti.com \
/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