From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: xor@freenetproject•org
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available
Date: Mon, 25 Jan 2016 13:03:17 +0100 [thread overview]
Message-ID: <20160125120317.GB17769@amethyst.visucore.com> (raw)
In-Reply-To: <1591452.8UA7xN1qih@1337h4x0r>
>
> So I'm interested whether this limitation has been lifted, and the whole
> feature is considered as finished.
Yes, it's exactly that limitation that has been lifted!
> If yes, I would highly recommend advertising it in the new release notes - as
> said, the disk space reduction is a big deal.
Good idea, has been added by Marco Falke in commit fa31133,
Wladimir
next prev parent reply other threads:[~2016-01-25 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 10:08 Wladimir J. van der Laan
2016-01-17 22:57 ` xor
2016-01-18 11:14 ` Wladimir J. van der Laan
2016-01-19 6:06 ` xor
2016-01-25 12:03 ` Wladimir J. van der Laan [this message]
2016-01-25 12:27 ` xor
2016-01-25 14:44 ` Marco Falke
2016-01-25 15:05 ` Wladimir J. van der Laan
2016-01-25 15:57 ` Simon Selitsky
2016-01-25 16:12 ` Jonas Schnelli
2016-01-25 17:33 ` xor
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=20160125120317.GB17769@amethyst.visucore.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=xor@freenetproject$(echo .)org \
/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