From: Brendan Molloy <brendan@bbqsrc.net>
To: John Smith <witchspace81@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge
Date: Fri, 17 Jun 2011 17:05:16 +1000 [thread overview]
Message-ID: <4DFAFCAC.80909@bbqsrc.net> (raw)
In-Reply-To: <BANLkTi=S0_K7kftB-+driDFiXBQ6LDhSPQ@mail.gmail.com>
Is there a link to this GUI code?
John Smith wrote:
> 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
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Regards,
Brendan Molloy
M: +61 434 069 776
T: @piecritic
W: http://bbqsrc.net
E: brendan@bbqsrc.net
next prev parent reply other threads:[~2011-06-17 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
2011-06-17 7:05 ` Brendan Molloy [this message]
2011-06-17 10:31 ` Pieter Wuille
2011-06-17 13:29 ` Luke-Jr
2011-06-17 14:10 ` Douglas Huff
2011-06-17 16:27 ` Gavin Andresen
2011-06-17 20:37 ` Luke-Jr
2011-06-17 22:59 ` Jeff Garzik
2011-06-19 0:30 ` Pieter Wuille
2011-06-20 2:34 ` [Bitcoin-development] Roadmap for autotools / Qt gui merge [Mac update] Mark Visser
2011-06-22 14:18 ` [Bitcoin-development] Roadmap for autotools / Qt gui merge Pieter Wuille
2011-06-19 1:37 ` Luke-Jr
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=4DFAFCAC.80909@bbqsrc.net \
--to=brendan@bbqsrc.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=witchspace81@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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