Skip to content
This repository has been archived by the owner on May 2, 2019. It is now read-only.

Highlight the existence of git 'tree' object type to distinguish it (e.g. from file system tree) #239

Merged
merged 1 commit into from Oct 5, 2013
Merged

Highlight the existence of git 'tree' object type to distinguish it (e.g. from file system tree) #239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion en/03-git-branching/01-chapter3.markdown
View file
Open in desktop
Expand Up @@ -15,7 +15,7 @@ To visualize this, let’s assume that you have a directory containing three fil
$ git add README test.rb LICENSE
$ git commit -m 'initial commit of my project'

When you create the commit by running `git commit`, Git checksums each subdirectory (in this case, just the root project directory) and stores those tree objects in the Git repository. Git then creates a commit object that has the metadata and a pointer to the root project tree so it can re-create that snapshot when needed.
Running `git commit` checksums all project directories and stores them as `tree` objects in the Git repository. Git then creates a `commit` object that has the metadata and a pointer to the root project `tree` object so it can re-create that snapshot when needed.

Your Git repository now contains five objects: one blob for the contents of each of your three files, one tree that lists the contents of the directory and specifies which file names are stored as which blobs, and one commit with the pointer to that root tree and all the commit metadata. Conceptually, the data in your Git repository looks something like Figure 3-1.

Expand Down