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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1R2gk5-0008FW-Vj
for bitcoin-development@lists.sourceforge.net;
Sun, 11 Sep 2011 09:54:26 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.47 as permitted sender)
client-ip=209.85.213.47; envelope-from=witchspace81@gmail.com;
helo=mail-yw0-f47.google.com;
Received: from mail-yw0-f47.google.com ([209.85.213.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R2gk3-0001ga-OA
for bitcoin-development@lists.sourceforge.net;
Sun, 11 Sep 2011 09:54:25 +0000
Received: by ywf7 with SMTP id 7so4486ywf.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 11 Sep 2011 02:54:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.196.18 with SMTP id t18mr430352ybf.349.1315734858187; Sun,
11 Sep 2011 02:54:18 -0700 (PDT)
Received: by 10.151.107.13 with HTTP; Sun, 11 Sep 2011 02:54:18 -0700 (PDT)
In-Reply-To: <CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
References: <CAL0fb61HrL8xe0yNG8_H0cEmVizzhg1pRe67aJmUPbGmLabYcA@mail.gmail.com>
<CAJNQ0svrwJF02sssMwLeN8gjc+h2-F8Bo3iOrwWJUM8NtWknFg@mail.gmail.com>
<CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
Date: Sun, 11 Sep 2011 09:54:18 +0000
Message-ID: <CAJNQ0svPNAZSRBm+O88p4Spw6MmQinuT_S15Z56jb3Z6VAorwQ@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Alex Waters <ampedal@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd487ccd7429f04aca764c8
X-Spam-Score: -0.5 (/)
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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
1.0 HTML_MESSAGE BODY: HTML included in message
-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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R2gk3-0001ga-OA
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: Sun, 11 Sep 2011 09:54:26 -0000
--000e0cd487ccd7429f04aca764c8
Content-Type: text/plain; charset=ISO-8859-1
Alex,
On Sun, Sep 11, 2011 at 7:45 AM, Alex Waters <ampedal@gmail.com> wrote:
> Hey John,
>
> It could be as simple as listing some things that you think could possibly
> break if qt is implemented. For example, "check the UI for artifacts". I
> don't really know what could potentially need to be tested, so any help
> would get things processed faster.
>
> I can't acknowledge a pull unless there is substantial evidence that it's
> been tested, especially something of this size...
>
It has been under development for a long time, the thread on the bitcointalk
forum is "substantial evidence" that many people are using it (also, I
receive quite a lot of mail about it, and the number of followers on github
steadily fluctuates around ~30). So nothing obvious is broken, at least, I
think has worked better than the Wx UI for quite a while.
But as I've said before I'm fine with keeping bitcoin-qt as a parallel,
experimental, release for a while. I think that's the only way to get more
testing with people that don't want to or can't build from source (could
just mark the download as "New GUI, experimental" or so...).
To be honest I think it should be merged at least as experimental ASAP, it
would save a lot of GUI complaints on the forum about things I've
implemented months ago already. However I will only put up a pull request as
soon as it is clear that it will actually be integrated. It is too much work
for me to keep the pull request up-to-date if it lingers for months like
many others have.
JS
--000e0cd487ccd7429f04aca764c8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Alex,<br><br><div class=3D"gmail_quote">On Sun, Sep 11, 2011 at 7:45 AM, Al=
ex Waters <span dir=3D"ltr"><<a href=3D"mailto:ampedal@gmail.com">ampeda=
l@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hey John,<div><br></div><div>It could be as simple as listing some things t=
hat you think could possibly break if qt is implemented. For example, "=
;check the UI for artifacts". I don't really know what could poten=
tially need to be tested, so any help would get things processed faster.=A0=
</div>
<div><br></div><div>I can't acknowledge a pull unless there is substant=
ial evidence that it's been tested, especially something of this size..=
.</div></blockquote><div><br>It has been under development for a long time,=
the thread on the bitcointalk forum is "substantial evidence" th=
at many people are using it (also, I receive quite a lot of mail about it, =
and the number of followers on github steadily fluctuates around ~30).=A0 S=
o nothing obvious is broken, at least, I think has worked better than the W=
x UI for quite a while.<br>
<br>But as I've said before I'm fine with keeping bitcoin-qt as a p=
arallel, experimental, release for a while.=A0 I think that's the only =
way to get more testing with people that don't want to or can't bui=
ld from source (could just mark the download as "New GUI, experimental=
" or so...).<br>
<br>To be honest I think it should be merged at least as experimental ASAP,=
it would save a lot of GUI complaints on the forum about things I've i=
mplemented months ago already. However I will only put up a pull request as=
soon as it is clear that it will actually be integrated. It is too much wo=
rk for me to keep the pull request up-to-date if it lingers for months like=
many others have.<br>
<br>JS<br><br></div></div>
--000e0cd487ccd7429f04aca764c8--
|
