git/Documentation/config/commitgraph.txt

commitGraph.readChangedPaths::
	If true, then git will use the changed-path Bloom filters in the
	commit-graph file (if it exists, and they are present). Defaults to
	true. See linkgit:git-commit-graph[1] for more information.
commit-graph: respect 'commitGraph.readChangedPaths' Git uses the 'core.commitGraph' configuration value to control whether or not the commit graph is used when parsing commits or performing a traversal. Now that commit-graphs can also contain a section for changed-path Bloom filters, administrators that already have commit-graphs may find it convenient to use those graphs without relying on their changed-path Bloom filters. This can happen, for example, during a staged roll-out, or in the event of an incident. Introduce 'commitGraph.readChangedPaths' to control whether or not Bloom filters are read. Note that this configuration is independent from both: - 'core.commitGraph', to allow flexibility in using all parts of a commit-graph _except_ for its Bloom filters. - The '--changed-paths' option for 'git commit-graph write', to allow reading and writing Bloom filters to be controlled independently. When the variable is set, pretend as if no Bloom data was specified at all. This avoids adding additional special-casing outside of the commit-graph internals. Suggested-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-09-09 17:23:10 +02:00			`commitGraph.readChangedPaths::`
			`If true, then git will use the changed-path Bloom filters in the`
			`commit-graph file (if it exists, and they are present). Defaults to`
			`true. See linkgit:git-commit-graph[1] for more information.`