1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
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 <luke@dashjr.org>) id 1RAoyG-0003ae-9B
for bitcoin-development@lists.sourceforge.net;
Mon, 03 Oct 2011 20:18:40 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RAoyD-0007Se-KI for bitcoin-development@lists.sourceforge.net;
Mon, 03 Oct 2011 20:18:40 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
[184.4.160.40]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 05AD7204032
for <bitcoin-development@lists.sourceforge.net>;
Mon, 3 Oct 2011 20:18:32 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Mon, 3 Oct 2011 16:17:52 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201110031617.54176.luke@dashjr.org>
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RAoyD-0007Se-KI
Subject: [Bitcoin-development] [PULLs] 6 branches
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: Mon, 03 Oct 2011 20:18:40 -0000
These branches are ready for merging to mainline.
Branches can be viewed at:
http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/heads
git pull git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin.git <branchname>
=
minfee_modes: minor internal API change as a step toward allowing
user-customizable fee schedules
=
qmake_system_crypto++: allow building bitcoin-qt against system crypto++
This is worthless if the crypto++ dependency is removed.
=
sharedlibs: build bitcoind against shared libraries on 'unix'
Not sure why it's been static for so long, but most systems only have
shared libs.
=
signal_blk_notify: -blknotifypidfile option to send SIGUSR1 to a PID when
there's a new best block
Used by basically every pool now, it just sends SIGUSR1 to a poolserver.
=
bugfix_qt_uri_amount_parser: fix URI amount parser to accept exponents and
hexadecimals
Please don't bother arguing over bugfix_qt_uri_amount_parser. It'll just
be a waste of time. Neither the pro- nor anti- sides have budged over
multiple arguments already. I can't force you guys to merge it, but I can
at least make it easy if you decide to tolerate it. Just keep in mind that
it doesn't hurt the BTC-only URIs at all, and if nobody ends up using it
for other units, it can always be removed later.
Best case scenario: people use it and bitcoin-qt works correctly
Worst case scenario: people don't use it, and it can be removed
=
base58_liberal_parsing: accept typos in base58 data
The same best/worst case scenario logic as the URI parser applies
to base58_liberal_parsing too, so long as typos aren't advertised as
legitimate addresses.
|
