Conversation
|
I didn't do this yet because people are reading the documentation on github, and having |
|
If it is the thing of the past, we should also remove the code behind it. We should probably also define some mechanism to deprecate features, announce to-be-deprecated features somehow. This is one thing, accounts the other etc. |
|
Linearize may remain useful for longer, especially with 0.10+'s out-of-order downloading and storage. Perhaps block chain analysis tools will no longer be able to work with the raw block files anymore, but linearize should always give very clean data to work with. |
|
I second @sipa's comments. The reports of bootstrap's death have been greatly exaggerated. Removing its documentation, even the code itself, appears premature. |
|
Don't get me wrong. I do not agree with the removal. It can be useful in many cases. |
|
My only point is that there is a distinction between removing the concept/recommendation of "using linearize to create a linear block data file" and "using said file to speed up initial download". |
|
Дорогой друг,что я удалил,Это не умышленно просто у меня мало опыта.Я даже 2014-12-14 1:24 GMT+03:00 paveljanik notifications@github.com:
|
|
@sipa Yes. I was talking about the import from the .dat file (https://github.com/bitcoin/bitcoin/blob/master/src/init.cpp#L429) in this case. |
|
No one is arguing for the linearize scripts to be removed. I'd certainly be opposed. But there is no use for a guide encouraging using the bootstrapping torent for normal users anymore. Importing from a .dat can also still be useful in exceptional circumstances, ie testing and troubleshooting. NACK on removing that. |
|
This is part of @theuni's trivial tree (https://github.com/theuni/bitcoin-trivial/commits/trivial-rebase) and will be merged via that route, so closing this pull. |
See discussion in #5455. Can be tagged for 0.11