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
|
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 <laanwj@gmail.com>) id 1RXE1z-0000fF-NG
for bitcoin-development@lists.sourceforge.net;
Sun, 04 Dec 2011 15:31:07 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.47 as permitted sender)
client-ip=209.85.210.47; envelope-from=laanwj@gmail.com;
helo=mail-pz0-f47.google.com;
Received: from mail-pz0-f47.google.com ([209.85.210.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RXE1z-0002O1-2T
for bitcoin-development@lists.sourceforge.net;
Sun, 04 Dec 2011 15:31:07 +0000
Received: by dake40 with SMTP id e40so4152520dak.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 04 Dec 2011 07:31:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.16.135 with SMTP id g7mr14828956pbd.65.1323012661128; Sun,
04 Dec 2011 07:31:01 -0800 (PST)
Received: by 10.143.92.15 with HTTP; Sun, 4 Dec 2011 07:31:01 -0800 (PST)
In-Reply-To: <201112040922.13744.luke@dashjr.org>
References: <CAJNQ0ssW4od3tA5vdASEs4KxZ7-UsxEjWT7NSc0dcWEzrkcH9w@mail.gmail.com>
<201112040922.13744.luke@dashjr.org>
Date: Sun, 4 Dec 2011 16:31:01 +0100
Message-ID: <CA+s+GJB197G+NaRgxG0VbUdbLS=SdoYjdmtaApQiALvn=+n73g@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=bcaec5215653b32c9104b345e319
X-Spam-Score: -0.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
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
X-Headers-End: 1RXE1z-0002O1-2T
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Closing issues on github
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, 04 Dec 2011 15:31:07 -0000
--bcaec5215653b32c9104b345e319
Content-Type: text/plain; charset=UTF-8
>
>
> I think it would be ideal if someone wanted to take up wxBitcoin. Maybe
> after
> backporting to wx 2.8...
>
Indeed, someone could do this if they're interested in it, in their own
fork. That's what I said too. But it's no longer our issue.
> > I don't think that has very high priority, and should probably not be in
> the
> > main project.
>
> Please be careful to avoid the centralization mindset. There is no "main
> project"; there is bitcoind, wxBitcoin, Bitcoin-Qt, MultiBit,
With the "main project" here I mean the issue list of bitcoin/bitcoin
project on github, which only deals with that project (and not that of the
forks, which have their own issue lists). You can argue the "main"-ness but
it's just a mailing list message and not some official document deciding
about the future of bitcoin, so I did not feel like specifying it to that
level of detail.
JS
--bcaec5215653b32c9104b345e319
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
I think it would be ideal if someone wanted to take up wxBitcoin. Maybe aft=
er<br>
backporting to wx 2.8...<br></blockquote><div><br></div><div>Indeed, someon=
e could do this if they're interested in it, in their own fork. That=
9;s what I said too. But it's no longer our issue.</div><div>=C2=A0</di=
v>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
> I don't think that has very high priority, and should probably not=
be in the<br>
> main project.<br>
<br>
Please be careful to avoid the centralization mindset. There is no "ma=
in<br>
project"; there is bitcoind, wxBitcoin, Bitcoin-Qt, MultiBit,</blockqu=
ote><div><br></div><div>With the "main project" here I mean the i=
ssue list of bitcoin/bitcoin project on github, which only deals with that =
project (and not that of the forks, which have their own issue lists).=C2=
=A0You can argue the "main"-ness but it's just a mailing list=
message and not some official document deciding about the future of bitcoi=
n, so I did not feel like specifying it to that level of detail.=C2=A0</div=
>
<div><br></div><div>JS</div><div><br></div></div>
--bcaec5215653b32c9104b345e319--
|
