public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
Date: Fri, 17 Jan 2014 12:44:09 +0100	[thread overview]
Message-ID: <CA+s+GJDeV9-djdEsA_stznNK9zzBA_0xQFV_m6tVygJicuLWuQ@mail.gmail.com> (raw)
In-Reply-To: <201401161523.38623.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

On Thu, Jan 16, 2014 at 4:23 PM, Luke-Jr <luke@dashjr.org> wrote:

>
> https://github.com/bitcoin/bitcoin/pulls/luke-jr
>
> These are pretty much all well-tested and stable for months now.
>

#3242: Autoconf improvements needs rebase, and comment from jgarzik and me
taken into account (about -enable-frontends=).

The others appear to be more controversial as they affect mining/consensus.
I'd really like to see ACKs from more reviewers and testers there before
merging.

Wladimir

[-- Attachment #2: Type: text/html, Size: 1211 bytes --]

  reply	other threads:[~2014-01-17 11:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  9:09 [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule Wladimir
2014-01-16 10:41 ` Warren Togami Jr.
2014-01-16 15:23 ` Luke-Jr
2014-01-17 11:44   ` Wladimir [this message]
2014-01-17 18:41     ` Luke-Jr
2014-01-17 20:53       ` Jeff Garzik
2014-01-17 21:04         ` Mark Friedenbach
2014-01-18 11:34           ` Jouke Hofman
2014-01-17 21:31         ` Luke-Jr
2014-01-18  8:11         ` Odinn Cyberguerrilla
2014-01-18 11:05           ` Wladimir
2014-01-18 11:28             ` Odinn Cyberguerrilla
2014-01-18 17:38             ` Mark Friedenbach
2014-01-19  2:53               ` Jeff Garzik
2014-01-19 10:24                 ` Wladimir
2014-01-23 11:10                   ` 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+GJDeV9-djdEsA_stznNK9zzBA_0xQFV_m6tVygJicuLWuQ@mail.gmail.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.org \
    /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