From: Gregory Maxwell <gmaxwell@gmail.com>
To: xor@freenetproject.org
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9.4 not on bitcoin.org?
Date: Sun, 1 Feb 2015 20:41:35 +0000 [thread overview]
Message-ID: <CAAS2fgTz55DbLEgHXXmWX-mxjWD8k4Omp9E+xJeWkhUw6Yribw@mail.gmail.com> (raw)
In-Reply-To: <2472472.uuMyyaUxq1@1337h4x0r>
On Sun, Feb 1, 2015 at 8:08 PM, xor <xor@freenetproject.org> wrote:
> Why is that?
Because Binaries on Bitcoin.org have always been unaffected by the
issue 0.9.4 was released to address.
> Also, is it correct that there wasn't a release candidate before the release?
> Sounds dangerous to me.
The changes were tried first by many people as part of git master.
This was narrow bug fix backport required to prevent the software from
no longer working at all for people who compiled it themselves and
received software updates for their system.
prev parent reply other threads:[~2015-02-01 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 20:08 [Bitcoin-development] Bitcoin Core 0.9.4 not on bitcoin.org? xor
2015-02-01 20:40 ` Wladimir
2015-02-01 20:41 ` Gregory Maxwell [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=CAAS2fgTz55DbLEgHXXmWX-mxjWD8k4Omp9E+xJeWkhUw6Yribw@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=xor@freenetproject.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