From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.7 release planning
Date: Sat, 11 Aug 2012 18:05:07 +0000 [thread overview]
Message-ID: <201208111805.09429.luke@dashjr.org> (raw)
In-Reply-To: <50268BB0.8080001@bitminter.com>
On Saturday, August 11, 2012 4:43:28 PM Geir Harald Hansen wrote:
> By the way, by far the most common support request I have at my pool is
> users withdrawing coins and not seeing it in their wallet because it's
> not up-to-date with the block chain. Might be worth adding something in
> the bitcoin-qt GUI to make it more obvious that users can't see new
> transactions and why.
Bitcoin-Qt even delays showing generation until 2 confirms.
> These two seem odd:
> Use UPnP to map the listening port (default: 0)
> Use UPnP to map the listening port (default: 1 when listening)
The default depends on build options, so that should be correct.
next prev parent reply other threads:[~2012-08-11 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 16:43 [Bitcoin-development] Version 0.7 release planning Jeff Garzik
2012-08-02 16:45 ` Jeff Garzik
2012-08-02 18:00 ` Gavin
2012-08-02 17:17 ` Luke-Jr
2012-08-11 16:43 ` Geir Harald Hansen
2012-08-11 18:05 ` Luke-Jr [this message]
2012-08-11 18:32 ` Wladimir
2012-08-11 18:56 ` Wladimir
2012-08-12 7:59 ` Geir Harald Hansen
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=201208111805.09429.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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