public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
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 13:12:15 +0200	[thread overview]
Message-ID: <CA+s+GJDiaxn_qOvdmKRKRgQ51QmQ8vfVi4=DAWu+tzTzpmt-Tg@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@mail.gmail.com>

On Thu, Oct 11, 2012 at 12:51 PM, Wladimir <laanwj@gmail.com> wrote:
> 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.

Oops, in my enthusiasm I completely forgot that 0.7.1 is still in rc, not final.

What I merged is:
- #1901 from laanwj/2012_10_remove_strlcpy
- #1900 from Diapolo/optionsmodel_getters
- #1913 from sipa/noi2p
- #1879 from sipa/fdatasync

I don't think any of them is problematic to have in rc2. If it is, we
need to make a branch for 0.7.x at eb49457 and consider master the
0.8.x branch.

Wladimir



      reply	other threads:[~2012-10-11 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 18:40 [Bitcoin-development] Post-0.7.1 tree freeze for ultraprune Jeff Garzik
2012-10-11 10:51 ` Wladimir
2012-10-11 11:12   ` Wladimir [this message]

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+GJDiaxn_qOvdmKRKRgQ51QmQ8vfVi4=DAWu+tzTzpmt-Tg@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --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