Deploy properly with Nokia Qt installer's Frameworks
Upgrading to 0.8: re-use blkNNNN.dat files.
If the prio. will be enough after the next block don't force fees.

  If the user was really after the fastest possible confirmation times
they would be manually setting a fee. In cases where the wallet builds
a transaction with a priority that is too low to qualify as free until
the next block, go ahead without a fee.  Confirmation frequently takes
multiple blocks even when a minimum fee is provided.
OutputDebugStringF code cleanup

Initialize the OutputDebugStringF mutex and file pointer using
boost::call_once, to be thread-safe.
Make the return value of OutputDebugStringF really be the number of
characters written (*printf() semantics).
Declare the fReopenDebugLog flag volatile, since it is changed from
a signal handler.
And don't declare OutputDebugStringF() as inline.
Display tx nLockTime correctly when set to block #

Previously when a transaction was set to lock at a specific block the
calculation was reversed, returning a negative number. This broke the UI
and caused it to display %n in place of the actual number.

In addition the previous calculation would display "Open for 0 blocks"
when the block height was such that the next block created would
finalize the transaction. Inserted the word "more" and changed the
calculation so that the last message would be "Open for 1 more block" to
better match user expectations.
Remove fClient

Client (SPV) mode never got implemented entirely, and whatever part was already
working, is likely not been tested (or even executed at all) for the past two
years. This removes it entirely.

If we want an SPV implementation, I think we should first get the block chain
data structures to be encapsulated in a class implementing a standard interface,
and then writing an alternate implementation with SPV semantics.
Bitcoin-Qt: use reference in setAddress_SM() and setAddress_VM()
Merge pull request #2166 from Diapolo/Qt_signverify

Bitcoin-Qt: use reference in setAddress_SM() and setAddress_VM()
make database init messages more valuable

- it was bad, that quite some messages were just talking about a database,
  I think a user should know, if we are talking about wallet db or
  block/coin db
- also adds a new init message for "Verifying block database integrity..."
Update development process README to reflect current reality
Merge branch 'devprocess'
Merge pull request #2142 from gavinandresen/utilprint

OutputDebugStringF code cleanup
Merge pull request #2099 from gavinandresen/blkfile_upgrade

Upgrading to 0.8: re-use blkNNNN.dat files.
Merge pull request #2161 from sipa/noclient

Remove fClient
Merge branch 'macdeployqt_fix' of git://github.com/themighty1/bitcoin
Merge pull request #2129 from gmaxwell/wallet_less_frequent_fees

If the prio. will be enough after the next block don't force fees. [wallet]
Merge pull request #2159 from petertodd/display-nlocktime-correctly

Display tx nLockTime correctly when set to block #
Merge pull request #2172 from Diapolo/init_messages

make database init messages more valuable