From: xor@freenetproject.org
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available
Date: Mon, 25 Jan 2016 18:33:09 +0100 [thread overview]
Message-ID: <20782747.nfdyibNE2U@1337h4x0r> (raw)
In-Reply-To: <20160125150559.GA28847@amethyst.visucore.com>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
On Monday, January 25, 2016 04:05:59 PM Wladimir J. van der Laan wrote:
> I don't have time to work on the release notes right now, but if someone
> else wants to contribute that'd be awesome.
I cooked my first pull request to resolve this:
https://github.com/bitcoin/bitcoin/pull/7416
Thanks for all the explanations you folks provided! :)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-01-25 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 10:08 [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available 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
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 [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=20782747.nfdyibNE2U@1337h4x0r \
--to=xor@freenetproject.org \
--cc=bitcoin-dev@lists.linuxfoundation.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