doc: use 'object database' not ODB or abbreviation
The abbreviation 'ODB' is used in the technical documentation sections for commit-graph and parallel-checkout, along with an 'odb' option in `git-pack-redundant`, without expansion. Use 'object database' in full, in those entries. The text has not been reflowed to keep the changes minimal. While in the glossary for `object` terms, add the common`oid` abbreviation to its entry. 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
fa8e8d5b31f2accfe956e9fd0f67ccb90586ed65
4 files changed
+4
-4
Documentation/git-pack-redundant.txt
+1
-1
@@ -34,7 +34,7 @@ OPTIONS
34
35
--alt-odb::
36
Don't require objects present in packs from alternate object
37
- directories to be present in local packs.
37
+ database (odb) directories to be present in local packs.
38
39
--verbose::
40
Outputs some statistics to stderr. Has a small performance penalty.
Documentation/glossary-content.txt
+1
-1
@@ -262,7 +262,7 @@ This commit is referred to as a "merge commit", or sometimes just a
262
identified by its <<def_object_name,object name>>. The objects usually
263
live in `$GIT_DIR/objects/`.
264
265
-[[def_object_identifier]]object identifier::
265
+[[def_object_identifier]]object identifier (oid)::
266
Synonym for <<def_object_name,object name>>.
267
268
[[def_object_name]]object name::
Documentation/technical/commit-graph.txt
+1
-1
@@ -17,7 +17,7 @@ There are two main costs here:
17
18
The commit-graph file is a supplemental data structure that accelerates
19
commit graph walks. If a user downgrades or disables the 'core.commitGraph'
20
-config setting, then the existing ODB is sufficient. The file is stored
20
+config setting, then the existing object database is sufficient. The file is stored
21
as "commit-graph" either in the .git/objects/info directory or in the info
22
directory of an alternate.
23
Documentation/technical/parallel-checkout.txt
+1
-1
@@ -56,7 +56,7 @@ Rejected Multi-Threaded Solution
56
57
The most "straightforward" implementation would be to spread the set of
58
to-be-updated cache entries across multiple threads. But due to the
59
-thread-unsafe functions in the ODB code, we would have to use locks to
59
+thread-unsafe functions in the object database code, we would have to use locks to
60
coordinate the parallel operation. An early prototype of this solution
61
showed that the multi-threaded checkout would bring performance
62
improvements over the sequential code, but there was still too much lock