[PATCH 3/6] user-manual: introduce the word "commit" earlier
From: J. Bruce Fields <hidden>
Date: 2016-06-15 22:43:31
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
From: J. Bruce Fields <redacted> Use the word "commit" as a synonym for "version" from the start. Signed-off-by: J. Bruce Fields <redacted> --- Documentation/user-manual.txt | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 933177a..6d35a1f 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt@@ -66,14 +66,14 @@ contains all the information about the history of the project. How to check out a different version of a project ------------------------------------------------- -Git is best thought of as a tool for storing the history of a -collection of files. It stores the history as a compressed -collection of interrelated snapshots (versions) of the project's -contents. +Git is best thought of as a tool for storing the history of a collection +of files. It stores the history as a compressed collection of +interrelated snapshots of the project's contents. In git each such +version is called a <<def_commit,commit>>. A single git repository may contain multiple branches. It keeps track of them by keeping a list of <<def_head,heads>> which reference the -latest version on each branch; the gitlink:git-branch[1] command shows +latest commit on each branch; the gitlink:git-branch[1] command shows you the list of branch heads: ------------------------------------------------
--
1.5.3.rc5.19.g0734d