From: "Luke-Jr" <luke@dashjr.org>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] 2012-02-17 next[-test]
Date: Fri, 17 Feb 2012 11:33:41 -0500 [thread overview]
Message-ID: <201202171133.42264.luke@dashjr.org> (raw)
849 gavin/testnetmining
852 Fix #846. Allow negative options in bitcoin.conf
719 coinbaser
^^ next ^^
834 sje/BackupWallet
570 force_send
806 sipa/threadid
816 sipa/lameversion
^^ 037497c ^^
854 laanwj/2012_02_qtipc
841 sipa/getalltransactions
787 sipa/addrman
823 sipa/nodupcon
829 sipa/multilocal
568 rpc_keepalive
565 optimize_FastGetWork
837 sje/ShowImmatureBalance
838 laanwj/201202_guiaddsuffix
853 laanwj/2012_02_altminimizetray
855 sje/ToggleHide
^^ 4b7e5f5 ^^
780 checkhashverify
715 bugfix_client_name
559 accept_nonstdtxn
552 base58_liberal_parsing
553 bugfix_qt_uri_amount_parser
562 optimize_ToHex
^^ next-test ^^
reply other threads:[~2012-02-17 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201202171133.42264.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