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>
Taylor Blau committedSep 9, 2020 at 11:23 UTCb66d84756f0f3704303ddc202707ac00037ace48
new file mode 100644index 0000000000..cff0797b54--- /dev/null+++ b/Documentation/config/commitgraph.txt@@ -0,0 +1,4 @@+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.c
+4-2
index 0c1030641c..a516e93d71 100644--- a/commit-graph.c+++ b/commit-graph.c@@ -320,6 +320,8 @@ struct commit_graph *parse_commit_graph(struct repository *r, return NULL; }+ prepare_repo_settings(r);+ graph = alloc_commit_graph(); graph->hash_len = the_hash_algo->rawsz;@@ -396,14 +398,14 @@ struct commit_graph *parse_commit_graph(struct repository *r, case GRAPH_CHUNKID_BLOOMINDEXES: if (graph->chunk_bloom_indexes) chunk_repeated = 1;- else+ else if (r->settings.commit_graph_read_changed_paths) graph->chunk_bloom_indexes = data + chunk_offset; break; case GRAPH_CHUNKID_BLOOMDATA: if (graph->chunk_bloom_data) chunk_repeated = 1;- else {+ else if (r->settings.commit_graph_read_changed_paths) { uint32_t hash_version; graph->chunk_bloom_data = data + chunk_offset; hash_version = get_be32(data + chunk_offset);
repo-settings.c
+3
index 0918408b34..9e551bc03d 100644--- a/repo-settings.c+++ b/repo-settings.c@@ -17,9 +17,12 @@ void prepare_repo_settings(struct repository *r) if (!repo_config_get_bool(r, "core.commitgraph", &value)) r->settings.core_commit_graph = value;+ if (!repo_config_get_bool(r, "commitgraph.readchangedpaths", &value))+ r->settings.commit_graph_read_changed_paths = value; if (!repo_config_get_bool(r, "gc.writecommitgraph", &value)) r->settings.gc_write_commit_graph = value; UPDATE_DEFAULT_BOOL(r->settings.core_commit_graph, 1);+ UPDATE_DEFAULT_BOOL(r->settings.commit_graph_read_changed_paths, 1); UPDATE_DEFAULT_BOOL(r->settings.gc_write_commit_graph, 1); if (!repo_config_get_int(r, "index.version", &value))
repository.h
+1
index 3c1f7d54bd..81759b7d27 100644--- a/repository.h+++ b/repository.h@@ -29,6 +29,7 @@ struct repo_settings { int initialized; int core_commit_graph;+ int commit_graph_read_changed_paths; int gc_write_commit_graph; int fetch_write_commit_graph;