On Thu, May 19, 2016 at 11:45 PM, David Turner <dtur...@twopensource.com> wrote: > +--strict:: > +--no-strict:: > + Strict mode makes index-helper verify the shared memory after > + it's created. If the result does not match what's read from > + $GIT_DIR/index, the shared memory is destroyed. This makes > + index-helper take more than double the amount of time required > + for reading an index, but because it will happen in the > + background, it's not noticable.
Slightly off-topic, but for big indexes, running by a script or something, then the window for reading/verifying is not big and this strict verification will become noticable. > `--strict` is enabled by default. .. so we probably still want --strict by default for now. After this feature exits the experimental stage, we can switch it off. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
