summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: f2327c6)
raw | patch | inline | side by side (parent: f2327c6)
author | J. Bruce Fields <bfields@citi.umich.edu> | |
Fri, 31 Aug 2007 03:10:05 +0000 (23:10 -0400) | ||
committer | J. Bruce Fields <bfields@citi.umich.edu> | |
Sun, 16 Sep 2007 02:13:31 +0000 (22:13 -0400) |
"git internals" sounds like something only git developers must know
about, but this stuff should be of wider interest. Rename the chapter
and give it a slightly friendlier introduction.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
about, but this stuff should be of wider interest. Rename the chapter
and give it a slightly friendlier introduction.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Documentation/user-manual.txt | patch | blob | history |
index f7457ef487c71b4e4bec564c5b65b1b12d6ce121..09d01817c26b2f3555f59cab4d6e83a281b9abcd 100644 (file)
contents of the commit, you are guaranteed that the commit can never change
without its name also changing.
-In fact, in <<git-internals>> we shall see that everything stored in git
+In fact, in <<git-concepts>> we shall see that everything stored in git
history, including file data and directory contents, is stored in an object
with a name that is a hash of its contents.
options mentioned above.
-[[git-internals]]
-Git internals
-=============
+[[git-concepts]]
+Git concepts
+============
-Git depends on two fundamental abstractions: the "object database", and
-the "current directory cache" aka "index".
+Git is built on a small number of simple but powerful ideas. While it
+is possible to get things done without understanding them, you will find
+git much more intuitive if you do.
+
+We start with the most important, the <<def_object_database,object
+database>> and the <<def_index,index>>.
[[the-object-database]]
The Object Database