diff options
| author | Wladimir <laanwj@gmail.com> | 2014-06-14 07:28:29 +0200 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-06-14 05:28:37 +0000 |
| commit | 556a92978e79ed8bf67c6d81b243a2cceef0cd93 (patch) | |
| tree | d383c0ef629bbdc4e6b62e5430db3364ac1c02ca | |
| parent | 3e406e07f09e2382791d63969faf8ae353ac731d (diff) | |
| download | pi-bitcoindev-556a92978e79ed8bf67c6d81b243a2cceef0cd93.tar.gz pi-bitcoindev-556a92978e79ed8bf67c6d81b243a2cceef0cd93.zip | |
Re: [Bitcoin-development] Going to tag 0.9.2 final
| -rw-r--r-- | 19/f459f3c40a632d2cf0fa14a2370482c8afcb61 | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/19/f459f3c40a632d2cf0fa14a2370482c8afcb61 b/19/f459f3c40a632d2cf0fa14a2370482c8afcb61 new file mode 100644 index 000000000..90c9cc371 --- /dev/null +++ b/19/f459f3c40a632d2cf0fa14a2370482c8afcb61 @@ -0,0 +1,78 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <laanwj@gmail.com>) id 1WvgW5-0006LB-1o + for bitcoin-development@lists.sourceforge.net; + Sat, 14 Jun 2014 05:28:37 +0000 +Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.213.174 as permitted sender) + client-ip=209.85.213.174; envelope-from=laanwj@gmail.com; + helo=mail-ig0-f174.google.com; +Received: from mail-ig0-f174.google.com ([209.85.213.174]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WvgW3-0003xc-9R + for bitcoin-development@lists.sourceforge.net; + Sat, 14 Jun 2014 05:28:37 +0000 +Received: by mail-ig0-f174.google.com with SMTP id h3so1244190igd.13 + for <bitcoin-development@lists.sourceforge.net>; + Fri, 13 Jun 2014 22:28:29 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.50.50.231 with SMTP id f7mr9753886igo.42.1402723709372; Fri, + 13 Jun 2014 22:28:29 -0700 (PDT) +Received: by 10.64.60.195 with HTTP; Fri, 13 Jun 2014 22:28:29 -0700 (PDT) +In-Reply-To: <CAJHLa0O0mXMJJ3sSD-U+XwJrJUtEtP0Ba0s4==hG9BsSRHR9qg@mail.gmail.com> +References: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com> + <2420822.WsmHDRmLtl@1337h4x0r> + <CAJHLa0O0mXMJJ3sSD-U+XwJrJUtEtP0Ba0s4==hG9BsSRHR9qg@mail.gmail.com> +Date: Sat, 14 Jun 2014 07:28:29 +0200 +Message-ID: <CA+s+GJAbSP77tab0neyhROTQuQ-hjjOtLJf+karAu5+2ENLwKA@mail.gmail.com> +From: Wladimir <laanwj@gmail.com> +To: Jeff Garzik <jgarzik@bitpay.com> +Content-Type: text/plain; charset=UTF-8 +X-Spam-Score: -1.6 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (laanwj[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature +X-Headers-End: 1WvgW3-0003xc-9R +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Sat, 14 Jun 2014 05:28:37 -0000 + +On Fri, Jun 13, 2014 at 10:12 PM, Jeff Garzik <jgarzik@bitpay.com> wrote: +> As a general principle, I agree. Other projects have translation +> freeze points to address this. Although it is a small holistic risk, +> in theory, someone could maliciously change strings at the last minute +> in a language maintainers don't know well. + +I was just doing what was always done. In practice, the translations +follow a very different cycle than the rest of the code. Entering +translations as well as reviewing them happens inside Transifex. + +Sure, someone could "maliciously change strings". It's typical that +this little bikeshedding topic attracts so much attention. + +But if it makes all of you happy I won't do the translation update. + +Wladimir + + |