From: Wladimir <laanwj@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Post-0.7.1 tree freeze for ultraprune
Date: Thu, 11 Oct 2012 12:51:55 +0200 [thread overview]
Message-ID: <CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> Proposal: following 0.7.1 release, freeze the tree. Do not pull
> anything, until ultraprune is pulled (or rejected, but I think the
> latter is unlikely).
Yes, I think this is a good idea. Getting ultraprune in should be a priority.
I've just pulled all the small stuff that was already ACKed for
post-0.7.1, so IMO the freeze can start.
Wladimir
next prev parent reply other threads:[~2012-10-11 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:40 Jeff Garzik
2012-10-11 10:51 ` Wladimir [this message]
2012-10-11 11:12 ` 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='CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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