Skip to content

Commit 3512193

Browse files
J. Bruce FieldsJunio C Hamano
authored andcommitted
user-manual: insert earlier of mention content-addressable architecture
The content-addressable design is too important not to be worth at least a brief mention a little earlier on. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu> Signed-off-by: Junio C Hamano <junkio@cox.net>
1 parent 1c95c56 commit 3512193

File tree

1 file changed

+15
-9
lines changed

1 file changed

+15
-9
lines changed

Documentation/user-manual.txt

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -391,15 +391,20 @@ index 8be626f..d7aac9d 100644
391391
As you can see, a commit shows who made the latest change, what they
392392
did, and why.
393393

394-
Every commit has a 40-hexdigit id, sometimes called the "object name"
395-
or the "SHA1 id", shown on the first line of the "git show" output.
396-
You can usually refer to a commit by a shorter name, such as a tag or a
397-
branch name, but this longer name can also be useful. Most
398-
importantly, it is a globally unique name for this commit: so if you
399-
tell somebody else the object name (for example in email), then you are
400-
guaranteed that name will refer to the same commit in their repository
401-
that it does in yours (assuming their repository has that commit at
402-
all).
394+
Every commit has a 40-hexdigit id, sometimes called the "object name" or the
395+
"SHA1 id", shown on the first line of the "git show" output. You can usually
396+
refer to a commit by a shorter name, such as a tag or a branch name, but this
397+
longer name can also be useful. Most importantly, it is a globally unique
398+
name for this commit: so if you tell somebody else the object name (for
399+
example in email), then you are guaranteed that name will refer to the same
400+
commit in their repository that it does in yours (assuming their repository
401+
has that commit at all). Since the object name is computed as a hash over the
402+
contents of the commit, you are guaranteed that the commit can never change
403+
without its name also changing.
404+
405+
In fact, in <<git-internals>> we shall see that everything stored in git
406+
history, including file data and directory contents, is stored in an object
407+
with a name that is a hash of its contents.
403408

404409
Understanding history: commits, parents, and reachability
405410
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -2155,6 +2160,7 @@ See gitlink:git-config[1] for more details on the configuration
21552160
options mentioned above.
21562161

21572162

2163+
[[git-internals]]
21582164
Git internals
21592165
=============
21602166

0 commit comments

Comments
 (0)