Tested so far by me, but more testing still to be done, as I know there are bugs with the re-asking code.
Is it too early to open a pull request when I know it's still needing more testing...?
Tested so far by me, but more testing still to be done, as I know there are bugs with the re-asking code.
Is it too early to open a pull request when I know it's still needing more testing...?
This one for sure includes too many non-relating commits.
All that are unrelated to "Download blocks from several peers concurrently" e.g.:
Don't mix different projects, just open a pull for one thing and this is intended to allow to download blocks from several peers at the same time, right? It's unlikely to get that pull merged ever in this state IMHO.
If you really need to depend on other pullrequests, please at least rebase on top of them. I was going to put this in next-test, but it conflicts too much with your other pullreqs...
These commits should be removed or merged under the real changes (only if they're real dependencies):
This makes debugg.log quieter during block chain catch up, so that it is easier to see the block download process.
Conflicts:
src/main.cpp
Conflicts:
src/main.cpp
src/net.h
Useful for developers who need to refer to futher back in debug.log history, but who don't want to
enable the -debug option and all the verbosity that comes with that.
Conflicts:
src/init.cpp
(and wrap lines)
Conflicts:
src/main.cpp