From 3a5152f08763fcd7982d399206060fca5edb0c32 Mon Sep 17 00:00:00 2001 From: Eden Hochbaum Date: Thu, 12 Jul 2018 12:28:38 -0500 Subject: [PATCH 1/2] Tree objects don't nec. point to trees > "A single tree object contains one or more tree entries" The language suggests that each tree object contains (at least one) reference to another tree object, which is wrong. --- book/10-git-internals/sections/objects.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/10-git-internals/sections/objects.asc b/book/10-git-internals/sections/objects.asc index ec076c7e3..9b5008e0e 100644 --- a/book/10-git-internals/sections/objects.asc +++ b/book/10-git-internals/sections/objects.asc @@ -125,7 +125,7 @@ blob The next type of Git object we'll examine is the _tree_, which solves the problem of storing the filename and also allows you to store a group of files together. Git stores content in a manner similar to a UNIX filesystem, but a bit simplified. All the content is stored as tree and blob objects, with trees corresponding to UNIX directory entries and blobs corresponding more or less to inodes or file contents. -A single tree object contains one or more tree entries, each of which contains a SHA-1 pointer to a blob or subtree with its associated mode, type, and filename. +A single tree object contains one or more entries, each containing a SHA-1 pointer to a blob or subtree with its associated mode, type, and filename. For example, the most recent tree in a project may look something like this: [source,console] From 45acefb0e72a19fb983a2a944de50e3b536033ff Mon Sep 17 00:00:00 2001 From: Eden Hochbaum Date: Fri, 13 Jul 2018 14:19:11 -0500 Subject: [PATCH 2/2] Update objects.asc --- book/10-git-internals/sections/objects.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/10-git-internals/sections/objects.asc b/book/10-git-internals/sections/objects.asc index 9b5008e0e..a934b77b7 100644 --- a/book/10-git-internals/sections/objects.asc +++ b/book/10-git-internals/sections/objects.asc @@ -125,7 +125,7 @@ blob The next type of Git object we'll examine is the _tree_, which solves the problem of storing the filename and also allows you to store a group of files together. Git stores content in a manner similar to a UNIX filesystem, but a bit simplified. All the content is stored as tree and blob objects, with trees corresponding to UNIX directory entries and blobs corresponding more or less to inodes or file contents. -A single tree object contains one or more entries, each containing a SHA-1 pointer to a blob or subtree with its associated mode, type, and filename. +A single tree object contains one or more entries, each of which is the SHA-1 hash of a blob or subtree with its associated mode, type, and filename. For example, the most recent tree in a project may look something like this: [source,console]