From: Un Ix <slashdevnull@hotmail•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Date: Sat, 14 Jun 2014 13:42:01 +0800 [thread overview]
Message-ID: <BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl> (raw)
In-Reply-To: <CA+s+GJAbSP77tab0neyhROTQuQ-hjjOtLJf+karAu5+2ENLwKA@mail.gmail.com>
How about a prize for anyone who can spot any "malicious" strings within next hour?
;-)
> On 14/06/2014, at 1:32 pm, "Wladimir" <laanwj@gmail•com> wrote:
>
>> 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
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2014-06-14 5:42 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
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 [this message]
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=BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl \
--to=slashdevnull@hotmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/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