1
0
Fork 0
mirror of https://github.com/git/git.git synced 2024-05-05 17:36:18 +02:00

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>
This commit is contained in:
Philip Oakley 2022-10-29 17:41:12 +01:00 committed by Taylor Blau
parent 63bba4fdd8
commit 776ba91a5e
3 changed files with 7 additions and 7 deletions

View File

@ -618,7 +618,7 @@ but risks losing recent work in the event of an unclean system shutdown.
* `loose-object` hardens objects added to the repo in loose-object form.
* `pack` hardens objects added to the repo in packfile form.
* `pack-metadata` hardens packfile bitmaps and indexes.
* `commit-graph` hardens the commit graph file.
* `commit-graph` hardens the commit-graph file.
* `index` hardens the index when it is modified.
* `objects` is an aggregate option that is equivalent to
`loose-object,pack`.

View File

@ -3,7 +3,7 @@ gitformat-commit-graph(5)
NAME
----
gitformat-commit-graph - Git commit graph format
gitformat-commit-graph - Git commit-graph format
SYNOPSIS
--------
@ -14,7 +14,7 @@ $GIT_DIR/objects/info/commit-graphs/*
DESCRIPTION
-----------
The Git commit graph stores a list of commit OIDs and some associated
The Git commit-graph stores a list of commit OIDs and some associated
metadata, including:
- The generation number of the commit.
@ -34,7 +34,7 @@ corresponding to the array position within the list of commit OIDs. Due
to some special constants we use to track parents, we can store at most
(1 << 30) + (1 << 29) + (1 << 28) - 1 (around 1.8 billion) commits.
== Commit graph files have the following format:
== Commit-graph files have the following format:
In order to allow extensions that add extra data to the graph, we organize
the body into "chunks" and provide a binary lookup table at the beginning

View File

@ -1,4 +1,4 @@
Git Commit Graph Design Notes
Git Commit-Graph Design Notes
=============================
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
required (such as merge base calculations, "git log --graph").
In practice, we expect some commits to be created recently and not stored
in the commit graph. We can treat these commits as having "infinite"
in the commit-graph. We can treat these commits as having "infinite"
generation number and walk until reaching commits with known generation
number.
@ -149,7 +149,7 @@ Design Details
helpful for these clones, anyway. The commit-graph will not be read or
written when shallow commits are present.
Commit Graphs Chains
Commit-Graphs Chains
--------------------
Typically, repos grow with near-constant velocity (commits per day). Over time,