1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1QymNp-0002Ww-LX
for bitcoin-development@lists.sourceforge.net;
Wed, 31 Aug 2011 15:07:17 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me
designates 173.246.101.161 as permitted sender)
client-ip=173.246.101.161;
envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me;
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1QymNo-0003wA-WF for bitcoin-development@lists.sourceforge.net;
Wed, 31 Aug 2011 15:07:17 +0000
Received: from [152.23.41.100] (MainCampusMid00353.1Xwireless.unc.edu
[152.23.41.100])
by mail.bluematt.me (Postfix) with ESMTPSA id 1E846BB4
for <bitcoin-development@lists.sourceforge.net>;
Wed, 31 Aug 2011 17:05:29 +0200 (CEST)
From: Matt Corallo <matt@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <CAJNQ0su7iRsQ2zPhXcd774TTqYzJGT+E9ss4D=6Ja3QSrpLdkw@mail.gmail.com>
References: <CAJNQ0su7iRsQ2zPhXcd774TTqYzJGT+E9ss4D=6Ja3QSrpLdkw@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature";
boundary="=-w5h5UybB92OssRDV9GC3"
Message-ID: <1314803146.2601.5.camel@BMThinkPad.lan.bluematt.me>
Mime-Version: 1.0
Resent-From: Matt Corallo <bitcoin-list@bluematt.me>
Resent-To: bitcoin-development@lists.sourceforge.net
Date: Wed, 31 Aug 2011 11:07:10 -0400
X-Mailer: Evolution 2.32.2
X-Spam-Score: -2.0 (--)
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 SPF_PASS SPF: sender matches SPF record
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1QymNo-0003wA-WF
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
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: Wed, 31 Aug 2011 15:07:17 -0000
--=-w5h5UybB92OssRDV9GC3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Wed, 2011-08-31 at 14:20 +0000, John Smith wrote:
> Hi,
>=20
> Bitcoin-qt is now feature complete (including wallet encryption), and
> has been tested for a while by various people without any major
> problems.
>=20
> It is now in status of feature freeze.
>=20
> The project builds on Windows, MacOSX and Linux using qmake.
>=20
> 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.
>=20
> So IMO, it is ready to be merged.
IMHO it should be merged right after 0.4 is pushed.
--=-w5h5UybB92OssRDV9GC3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAABAgAGBQJOXk2/AAoJEBrh01BD4I5UiOkP/R7uPMxBZJVpsu/+HrcfnaYc
FFibp+9U0btplP1Uu/1Wr704LX5mObWIzfSQ4aTvI30DuNonSmt8wBRlyfR8N4Kb
L897vqYAcwLb5mSDCKv3NWusxtldLhYq1fqo3IeDDgSPZUJM8ivZ5vjQkRA+Bbhw
EZMaQWFsfpE3/HU2fanlqYPKOjnUEu+22riGarskYiT7MrOqIm0Q65aWeIoX4s2d
s036Gbjlf68XMfR88vDy1QasrLFunwPW0Huh05bfHtULH/TWukwK5T+LyeUL1wrK
T40wnBPgnf8bEtGjCdM/mBaz0K3Ysh2p4yKi4U5ZYVy10MlpgLVZUvqVod9EO2fR
KMRoM2M3UoowuoUkYJ5q7Rq71wBV34KUwQJ2ueS5YV1oP//ElF74XFfJaKUPsFEt
5rYQq5iS4n8yTyocQtt+aES01aYbfsDTyTD9dG+11x2vEIZ8zBrWbYPZIbzrgDSq
A5TFS5KuBKBE9YWl8FyoI310izaUz8iOaGcjMRLBaZvYrT7WqjOv2TMcis8J/VV1
vFHuxFTZTOt2Bt7Qlxv0FtYb8lek7Q0wpggPCxZLoC5Lefgn4GjUJD6YKBQzPZdB
IuEn8fnNeqHymOtjsI+Hflz8eaXJKPUsPUSMY6rAG/C1F0xT6OKpN9DUccenjgi/
E/g8l940Bk3kKefQWhw4
=ilyd
-----END PGP SIGNATURE-----
--=-w5h5UybB92OssRDV9GC3--
|
