diff options
author | Taylor Blau <me@ttaylorr.com> | 2020-04-13 22:04:17 -0600 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-04-15 09:20:28 -0700 |
commit | 8a6ac287b2ba5f75bb2d9409dd97e9b501daf253 (patch) | |
tree | ed0fc9f67c9d9369cd12530cf885da21128d797d /prompt.h | |
parent | builtin/commit-graph.c: introduce split strategy 'no-merge' (diff) | |
download | tgif-8a6ac287b2ba5f75bb2d9409dd97e9b501daf253.tar.xz |
builtin/commit-graph.c: introduce split strategy 'replace'
When using split commit-graphs, it is sometimes useful to completely
replace the commit-graph chain with a new base.
For example, consider a scenario in which a repository builds a new
commit-graph incremental for each push. Occasionally (say, after some
fixed number of pushes), they may wish to rebuild the commit-graph chain
with all reachable commits.
They can do so with
$ git commit-graph write --reachable
but this removes the chain entirely and replaces it with a single
commit-graph in 'objects/info/commit-graph'. Unfortunately, this means
that the next push will have to move this commit-graph into the first
layer of a new chain, and then write its new commits on top.
Avoid such copying entirely by allowing the caller to specify that they
wish to replace the entirety of their commit-graph chain, while also
specifying that the new commit-graph should become the basis of a fresh,
length-one chain.
This addresses the above situation by making it possible for the caller
to instead write:
$ git commit-graph write --reachable --split=replace
which writes a new length-one chain to 'objects/info/commit-graphs',
making the commit-graph incremental generated by the subsequent push
relatively cheap by avoiding the aforementioned copy.
In order to do this, remove an assumption in 'write_commit_graph_file'
that chains are always at least two incrementals long.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'prompt.h')
0 files changed, 0 insertions, 0 deletions