summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a5f90f3)
raw | patch | inline | side by side (parent: a5f90f3)
author | J. Bruce Fields <bfields@citi.umich.edu> | |
Sun, 19 Aug 2007 02:16:24 +0000 (22:16 -0400) | ||
committer | J. Bruce Fields <bfields@citi.umich.edu> | |
Sun, 26 Aug 2007 14:35:16 +0000 (10:35 -0400) |
Use the word "commit" as a synonym for "version" from the start.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Documentation/user-manual.txt | patch | blob | history |
index 933177a38b75ab2b55c28f74cff3c7dc6894983b..6d35a1f58baf0a1d3760753fdd87c2509e87cd88 100644 (file)
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:
------------------------------------------------