Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <witchspace81@gmail.com>) id 1QXSlI-0004Yd-Ip
	for bitcoin-development@lists.sourceforge.net;
	Fri, 17 Jun 2011 06:42:36 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.175 as permitted sender)
	client-ip=209.85.160.175; envelope-from=witchspace81@gmail.com;
	helo=mail-gy0-f175.google.com; 
Received: from mail-gy0-f175.google.com ([209.85.160.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1QXSlH-0002TK-Oc
	for bitcoin-development@lists.sourceforge.net;
	Fri, 17 Jun 2011 06:42:36 +0000
Received: by gyd5 with SMTP id 5so788834gyd.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 16 Jun 2011 23:42:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.88.12 with SMTP id q12mr2031455ybl.271.1308292950278; Thu,
	16 Jun 2011 23:42:30 -0700 (PDT)
Received: by 10.151.142.9 with HTTP; Thu, 16 Jun 2011 23:42:30 -0700 (PDT)
Date: Fri, 17 Jun 2011 06:42:30 +0000
Message-ID: <BANLkTi=S0_K7kftB-+driDFiXBQ6LDhSPQ@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=000e0cd7221a90412b04a5e2b0ee
X-Spam-Score: 1.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 freemail (witchspace81[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	2.2 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 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain
	0.0 T_TO_NO_BRKTS_FREEMAIL T_TO_NO_BRKTS_FREEMAIL
X-Headers-End: 1QXSlH-0002TK-Oc
Subject: [Bitcoin-development] Roadmap for autotools / Qt gui merge
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: Fri, 17 Jun 2011 06:42:36 -0000

--000e0cd7221a90412b04a5e2b0ee
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I think my Qt GUI is pretty much ready for merging. I've been using it for a
while and all functionality works.

What is the current roadmap for including the autotools build system, so
that it will be possible to support multiple GUIs? 0.4.0?

JS

--000e0cd7221a90412b04a5e2b0ee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,<br><br>I think my Qt GUI is pretty much ready for merging. I&#39;ve =
been using it for a while and all functionality works.<br><br>What is the c=
urrent roadmap for including the autotools build system, so that it will be=
 possible to support multiple GUIs? 0.4.0?<br>
<br>JS<br>

--000e0cd7221a90412b04a5e2b0ee--