From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] [PULLs] 6 branches
Date: Mon, 3 Oct 2011 16:17:52 -0400 [thread overview]
Message-ID: <201110031617.54176.luke@dashjr.org> (raw)
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.
reply other threads:[~2011-10-03 20:18 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=201110031617.54176.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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