From: Wladimir <laanwj@gmail•com>
To: Odinn Cyberguerrilla <odinn.cyberguerrilla@riseup•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
Date: Sat, 18 Jan 2014 12:05:30 +0100 [thread overview]
Message-ID: <CA+s+GJCwB3Jj7z32_5NCHgf7utyx0nm-fXiSW+79w8u4mi7W5g@mail.gmail.com> (raw)
In-Reply-To: <61c05e986b4d1010d0cf76868db7d2af.squirrel@fruiteater.riseup.net>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Sat, Jan 18, 2014 at 9:11 AM, Odinn Cyberguerrilla <
odinn.cyberguerrilla@riseup•net> wrote:
> <ABISprotocol hat: on>
>
> regarding:
> stuff not getting into blockchain in a day's time,
> microdonations not facilitated as much as they could be,
>
Please point to your pull requests improving these issues.
If your organization didn't contribute anything to further these issues
then there can't be much surprise that they didn't make it in, either.
that would be:
>
> very bad
> much news
> such fail
>
> Seriously, that would not be so good.
>
> Hope I made you laugh a bit
>
So it's more like a jester's hat then :)
How did I end up on the dogecoin-development list?!?
Wladimir
[-- Attachment #2: Type: text/html, Size: 1455 bytes --]
next prev parent reply other threads:[~2014-01-18 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 9:09 Wladimir
2014-01-16 10:41 ` Warren Togami Jr.
2014-01-16 15:23 ` Luke-Jr
2014-01-17 11:44 ` Wladimir
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 [this message]
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+GJCwB3Jj7z32_5NCHgf7utyx0nm-fXiSW+79w8u4mi7W5g@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=odinn.cyberguerrilla@riseup$(echo .)net \
/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