Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VnwDb-0003py-50 for bitcoin-development@lists.sourceforge.net; Tue, 03 Dec 2013 20:05:15 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VnwDZ-0003x3-Pf for bitcoin-development@lists.sourceforge.net; Tue, 03 Dec 2013 20:05:15 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VnwDQ-0004Fm-6c for bitcoin-development@lists.sourceforge.net; Tue, 03 Dec 2013 21:05:04 +0100 Received: from 201-69-230-106.dial-up.telesp.net.br ([201.69.230.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Dec 2013 21:05:04 +0100 Received: from fragabr by 201-69-230-106.dial-up.telesp.net.br with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Dec 2013 21:05:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: =?UTF-8?B?RMOibmllbA==?= Fraga Date: Tue, 3 Dec 2013 17:59:10 -0200 Organization: http://www.youtube.com/DanielFragaBR Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 201-69-230-106.dial-up.telesp.net.br X-Newsreader: Claws Mail 3.9.0cvs128 (GTK+ 2.24.20; x86_64-unknown-linux-gnu) X-Spam-Score: -0.3 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -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 (fragabr[at]gmail.com) -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: mcxnow.com] 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1VnwDZ-0003x3-Pf Subject: [Bitcoin-development] Suggestion: easy way to restore wallet.dat backup X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 20:05:15 -0000 I posted this on bitcoin-user, but nobody replied, so I'm trying here. Today, when a user uses bitcoin-qt client, it can make a backup of wallet.dat easily through menu, but when he/she needs to restore this backup, he/she must copy the file to the correct folder and execute "bitcoin-qt -rescan". My suggestion: bitcoin-qt developers could implement an easier way to restore. For example: a option in the File menu "Restore Wallet" or "Recover Wallet" where it would show a dialog asking for the backup file and everything would be done automatically (no need to do it manually). If we want everybody to use bitcoin, these operations should be as easy as possible. What do you think? -- Linux 3.12.0: One Giant Leap for Frogkind http://www.youtube.com/DanielFragaBR http://mcxnow.com Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL