From: Rusty Russell <rusty@rustcorp•com.au>
To: Btc Drak <btcdrak@gmail•com>, Jonathan Toomim <j@toom•im>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
bitcoin-xt <bitcoin-xt@googlegroups•com>
Subject: Re: [bitcoin-dev] Memory leaks?
Date: Fri, 23 Oct 2015 17:11:49 +1030 [thread overview]
Message-ID: <87fv12axxu.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CADJgMzvVJQxaoB7m=voo60whG4NQGV2jf0riN4QoM8eLGABxkA@mail.gmail.com>
Btc Drak via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> writes:
> I think this thread has gotten to the stage where it should be moved
> to an issue on Github and not continue to CC the bitcoin-dev list (or
> any other list tbh).
Agreed. I couldn't see an issue, so I've opened one. Let's track this
there, please.
https://github.com/bitcoin/bitcoin/issues/6876
Cheers,
Rusty.
next prev parent reply other threads:[~2015-10-23 6:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:56 Jonathan Toomim (Toomim Bros)
2015-10-13 22:49 ` odinn
2015-10-13 23:14 ` Jonathan Toomim (Toomim Bros)
2015-10-13 23:52 ` Dave Scotese
2015-10-14 0:08 ` Jonathan Toomim (Toomim Bros)
2015-10-14 0:25 ` Dave Scotese
2015-10-13 23:59 ` odinn
2015-10-14 7:22 ` Pavel Janík
2015-10-14 7:58 ` Tom Zander
2015-10-14 9:09 ` Mike Hearn
2015-10-14 15:19 ` odinn
2015-10-14 9:39 ` Wladimir J. van der Laan
2015-10-18 15:59 ` Jonathan Toomim
2015-10-19 19:17 ` Multipool Admin
2015-10-19 22:24 ` Multipool Admin
2015-10-20 10:12 ` Mike Hearn
2015-10-20 12:39 ` Jonathan Toomim
2015-10-21 3:01 ` Jonathan Toomim
2015-10-21 7:29 ` Tom Zander
2015-10-21 17:58 ` Jonathan Toomim
2015-10-22 16:06 ` Multipool Admin
2015-10-22 16:27 ` Jonathan Toomim
2015-10-22 17:01 ` Btc Drak
2015-10-23 6:41 ` Rusty Russell [this message]
2015-10-21 7:59 ` Ross Bennetts
2015-10-17 4:37 ` admin
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=87fv12axxu.fsf@rustcorp.com.au \
--to=rusty@rustcorp$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-xt@googlegroups$(echo .)com \
--cc=btcdrak@gmail$(echo .)com \
--cc=j@toom$(echo .)im \
/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