Correct indentation #4109

Correct indentation.

ACK, did a diff and checked, just indentation fixes.

Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/6b29ccc9f9a166b54a9a0a026debe6244b77d805 for binaries and test log.

This could happen for one of several reasons:

1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts (please tweak those patches in qa/pull-tester)
2. It adds/modifies tests which test network rules (thanks for doing that), which conflicts with a patch applied at test time
3. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
4. The test suite fails on either Linux i386 or Win32
5. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)

If you believe this to be in error, please ping BlueMatt on freenode or TheBlueMatt here.

This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.

It's uncommon to indent namspace blocks, because when they're used persistently, you often get entire .h files which are indented 2-3 levels.

I'm not against this (as I agree it improves readability in this case), but if we want to increase the use of namespaces (I think we should), this is perhaps not a good idea. Opinions, @laanwj ?

Agree @sipa. I think it can make sense to indent inner/nested namespaces, to distinguish them, but not the ones that surround the entire header/compilation unit.

So in this case ACK for indenting the "internal stuff" only.