doc: use "commit-graph" hyphenation consistently
Note, historical release notes have not been updated. Signed-off-by: Philip Oakley <philipoakley@iee.email> Signed-off-by: Taylor Blau <me@ttaylorr.com>
Philip Oakley committed
Oct 29, 2022 at 17:41 UTC
776ba91a5e3349479139e9a51a135d4bc838b613
3 files changed
+7
-7
Documentation/config/core.txt
+1
-1
@@ -618,7 +618,7 @@ but risks losing recent work in the event of an unclean system shutdown.
618
* `loose-object` hardens objects added to the repo in loose-object form.
619
* `pack` hardens objects added to the repo in packfile form.
620
* `pack-metadata` hardens packfile bitmaps and indexes.
621
-* `commit-graph` hardens the commit graph file.
621
+* `commit-graph` hardens the commit-graph file.
622
* `index` hardens the index when it is modified.
623
* `objects` is an aggregate option that is equivalent to
624
`loose-object,pack`.
Documentation/gitformat-commit-graph.txt
+3
-3
@@ -3,7 +3,7 @@ gitformat-commit-graph(5)
3
4
NAME
5
----
6
-gitformat-commit-graph - Git commit graph format
6
+gitformat-commit-graph - Git commit-graph format
7
8
SYNOPSIS
9
--------
@@ -14,7 +14,7 @@ $GIT_DIR/objects/info/commit-graphs/*
14
DESCRIPTION
15
-----------
16
17
-The Git commit graph stores a list of commit OIDs and some associated
17
+The Git commit-graph stores a list of commit OIDs and some associated
18
metadata, including:
19
20
- The generation number of the commit.
@@ -34,7 +34,7 @@ corresponding to the array position within the list of commit OIDs. Due
34
to some special constants we use to track parents, we can store at most
35
(1 << 30) + (1 << 29) + (1 << 28) - 1 (around 1.8 billion) commits.
36
37
-== Commit graph files have the following format:
37
+== Commit-graph files have the following format:
38
39
In order to allow extensions that add extra data to the graph, we organize
40
the body into "chunks" and provide a binary lookup table at the beginning
Documentation/technical/commit-graph.txt
+3
-3
@@ -1,4 +1,4 @@
1
-Git Commit Graph Design Notes
1
+Git Commit-Graph Design Notes
2
=============================
3
4
Git walks the commit graph for many reasons, including:
@@ -95,7 +95,7 @@ with default order), but is not used when the topological order is
95
required (such as merge base calculations, "git log --graph").
96
97
In practice, we expect some commits to be created recently and not stored
98
-in the commit graph. We can treat these commits as having "infinite"
98
+in the commit-graph. We can treat these commits as having "infinite"
99
generation number and walk until reaching commits with known generation
100
number.
101
@@ -149,7 +149,7 @@ Design Details
149
helpful for these clones, anyway. The commit-graph will not be read or
150
written when shallow commits are present.
151
152
-Commit Graphs Chains
152
+Commit-Graphs Chains
153
--------------------
154
155
Typically, repos grow with near-constant velocity (commits per day). Over time,