]> git.ipfire.org Git - thirdparty/git.git/blame - Documentation/git-commit-graph.txt
Merge branch 'js/pu-to-seen'
[thirdparty/git.git] / Documentation / git-commit-graph.txt
CommitLineData
4ce58ee3
DS
1git-commit-graph(1)
2===================
3
4NAME
5----
4c399442 6git-commit-graph - Write and verify Git commit-graph files
4ce58ee3 7
f237c8b6
DS
8
9SYNOPSIS
10--------
11[verse]
73716122
GS
12'git commit-graph verify' [--object-dir <dir>] [--shallow] [--[no-]progress]
13'git commit-graph write' <options> [--object-dir <dir>] [--[no-]progress]
f237c8b6
DS
14
15
16DESCRIPTION
17-----------
18
4c399442 19Manage the serialized commit-graph file.
f237c8b6
DS
20
21
22OPTIONS
23-------
24--object-dir::
4c399442 25 Use given directory for the location of packfiles and commit-graph
f237c8b6 26 file. This parameter exists to specify the location of an alternate
d59a9168 27 that only has the objects directory, not a full `.git` directory. The
c2bc6e6a 28 commit-graph file is expected to be in the `<dir>/info` directory and
0bd52e27
TB
29 the packfiles are expected to be in `<dir>/pack`. If the directory
30 could not be made into an absolute path, or does not match any known
31 object directory, `git commit-graph ...` will exit with non-zero
32 status.
f237c8b6 33
73716122
GS
34--[no-]progress::
35 Turn progress on/off explicitly. If neither is specified, progress is
36 shown if standard error is connected to a terminal.
f237c8b6
DS
37
38COMMANDS
39--------
40'write'::
41
4c399442 42Write a commit-graph file based on the commits found in packfiles.
049d51a2
DS
43+
44With the `--stdin-packs` option, generate the new commit graph by
3d5df01b 45walking objects only in the specified pack-indexes. (Cannot be combined
59fb8770 46with `--stdin-commits` or `--reachable`.)
3d5df01b
DS
47+
48With the `--stdin-commits` option, generate the new commit graph by
49walking commits starting at the commits specified in stdin as a list
2f00c355
TB
50of OIDs in hex, one OID per line. OIDs that resolve to non-commits
51(either directly, or by peeling tags) are silently ignored. OIDs that
52are malformed, or do not exist generate an error. (Cannot be combined
53with `--stdin-packs` or `--reachable`.)
59fb8770
DS
54+
55With the `--reachable` option, generate the new commit graph by walking
56commits starting at all refs. (Cannot be combined with `--stdin-commits`
57or `--stdin-packs`.)
7547b95b
DS
58+
59With the `--append` option, include all commits that are present in the
60existing commit-graph file.
c2bc6e6a 61+
d38e07b8 62With the `--changed-paths` option, compute and write information about the
1aa7b686 63paths changed between a commit and its first parent. This operation can
d38e07b8
GS
64take a while on large repositories. It provides significant performance gains
65for getting history of a directory or a file with `git log -- <path>`.
66+
4f027355
TB
67With the `--split[=<strategy>]` option, write the commit-graph as a
68chain of multiple commit-graph files stored in
69`<dir>/info/commit-graphs`. Commit-graph layers are merged based on the
70strategy and other splitting options. The new commits not already in the
71commit-graph are added in a new "tip" file. This file is merged with the
72existing file if the following merge conditions are met:
ce3614c3 73+
fdbde82f 74* If `--split=no-merge` is specified, a merge is never performed, and
8a6ac287
TB
75the remaining options are ignored. `--split=replace` overwrites the
76existing chain with a new one. A bare `--split` defers to the remaining
77options. (Note that merging a chain of commit graphs replaces the
78existing chain with a length-1 chain where the first and only
fdbde82f 79incremental holds the entire graph).
c2bc6e6a
DS
80+
81* If `--size-multiple=<X>` is not specified, let `X` equal 2. If the new
82tip file would have `N` commits and the previous tip has `M` commits and
83`X` times `N` is greater than `M`, instead merge the two files into a
84single file.
85+
86* If `--max-commits=<M>` is specified with `M` a positive integer, and the
87new tip file would have more than `M` commits, then instead merge the new
88tip with the previous tip.
89+
90Finally, if `--expire-time=<datetime>` is not specified, let `datetime`
91be the current time. After writing the split commit-graph, delete all
92unused commit-graph whose modified times are older than `datetime`.
f237c8b6 93
283e68c7
DS
94'verify'::
95
96Read the commit-graph file and verify its contents against the object
97database. Used to check for corrupted data.
3da4b609
DS
98+
99With the `--shallow` option, only check the tip commit-graph file in
100a chain of split commit-graphs.
283e68c7 101
f237c8b6
DS
102
103EXAMPLES
104--------
105
4c399442 106* Write a commit-graph file for the packed commits in your local `.git`
d59a9168 107 directory.
f237c8b6
DS
108+
109------------------------------------------------
110$ git commit-graph write
111------------------------------------------------
112
4893d717
113* Write a commit-graph file, extending the current commit-graph file
114 using commits in `<pack-index>`.
049d51a2
DS
115+
116------------------------------------------------
117$ echo <pack-index> | git commit-graph write --stdin-packs
118------------------------------------------------
119
4893d717 120* Write a commit-graph file containing all reachable commits.
3d5df01b
DS
121+
122------------------------------------------------
123$ git show-ref -s | git commit-graph write --stdin-commits
124------------------------------------------------
125
4893d717 126* Write a commit-graph file containing all commits in the current
d59a9168 127 commit-graph file along with those reachable from `HEAD`.
7547b95b
DS
128+
129------------------------------------------------
130$ git rev-parse HEAD | git commit-graph write --stdin-commits --append
131------------------------------------------------
132
f237c8b6 133
4ce58ee3
DS
134GIT
135---
136Part of the linkgit:git[1] suite