From: "Pavel Janík" <Pavel@Janik•cz>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Date: Fri, 13 Jun 2014 13:21:47 +0200 [thread overview]
Message-ID: <DAD7ABE9-E7E0-4F1E-8BFA-611F8B54CE61@Janik.cz> (raw)
In-Reply-To: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com>
Wladimir,
On Jun 13, 2014, at 12:18 PM, Wladimir wrote:
> If I do not hear anything, I will do a last-minute language import
this import can actually break things. I'd avoid it.
--
Pavel Janík
next prev parent reply other threads:[~2014-06-13 11:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 10:18 Wladimir
2014-06-13 11:21 ` Pavel Janík [this message]
2014-06-13 11:58 ` Wladimir
2014-06-13 12:02 ` Pavel Janík
2014-06-13 19:24 ` xor
2014-06-13 20:06 ` Matt Whitlock
2014-06-13 20:12 ` Jeff Garzik
2014-06-14 5:28 ` Wladimir
2014-06-14 5:42 ` Un Ix
2014-06-14 5:49 ` Matt Whitlock
2014-06-14 5:58 ` Un Ix
2014-06-14 6:01 ` Mark Friedenbach
2014-06-14 6:12 ` Wladimir
2014-06-14 6:23 ` 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=DAD7ABE9-E7E0-4F1E-8BFA-611F8B54CE61@Janik.cz \
--to=pavel@janik$(echo .)cz \
--cc=bitcoin-development@lists$(echo .)sourceforge.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