From: Matt Corallo <matt@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
Date: Wed, 31 Aug 2011 11:07:10 -0400 [thread overview]
Message-ID: <1314803146.2601.5.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <CAJNQ0su7iRsQ2zPhXcd774TTqYzJGT+E9ss4D=6Ja3QSrpLdkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On Wed, 2011-08-31 at 14:20 +0000, John Smith wrote:
> Hi,
>
> Bitcoin-qt is now feature complete (including wallet encryption), and
> has been tested for a while by various people without any major
> problems.
>
> It is now in status of feature freeze.
>
> The project builds on Windows, MacOSX and Linux using qmake.
>
> Impact to the core bitcoin functions is still minimal, and it can
> co-exist with Wx in the source tree. The only thing it lacks compared
> to the Wx GUI is translations, currently we only have English, Dutch
> and Russian.
Would it be possible to port some of the existing translations?
Something is better than nothing so some text that is close to the wx
version can just be copied.
Though IMHO its not a huge deal if qt is merged without all the
translations as IMHO it should be merged soon and then not the default
release GUI until its in tree for a bit (like one release) and some
translations can be built up.
>
> So IMO, it is ready to be merged.
IMHO it should be merged right after 0.4 is pushed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-08-31 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 14:20 John Smith
2011-08-31 15:07 ` Matt Corallo [this message]
2011-09-01 2:11 ` John Smith
2011-09-01 2:13 ` Luke-Jr
2011-09-01 2:32 ` John Smith
2011-09-22 20:11 ` Luke-Jr
2011-09-11 0:20 Alex Waters
2011-09-11 7:37 ` John Smith
[not found] ` <CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
2011-09-11 9:54 ` John Smith
2011-09-11 17:12 ` Gavin Andresen
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=1314803146.2601.5.camel@BMThinkPad.lan.bluematt.me \
--to=matt@bluematt$(echo .)me \
--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