diff options
author | Horst H. von Brand <vonbrand@inf.utfsm.cl> | 2006-06-03 16:27:26 -0400 |
---|---|---|
committer | Junio C Hamano <junkio@cox.net> | 2006-06-03 23:54:55 -0700 |
commit | abda1ef590d94a5e15e7ce3b685b5c092a790cfa (patch) | |
tree | 73162a92b2abd5d87b86566899e321dd8ccef59c /Documentation/core-tutorial.txt | |
parent | 895f10c3b596ef955c7f252717e5b4668530c569 (diff) | |
download | git-abda1ef590d94a5e15e7ce3b685b5c092a790cfa.tar.gz |
Documentation: Spelling fixes
Signed-off-by: Horst H. von Brand <vonbrand@inf.utfsm.cl>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/core-tutorial.txt')
-rw-r--r-- | Documentation/core-tutorial.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt index 5a831adf43..1185897f70 100644 --- a/Documentation/core-tutorial.txt +++ b/Documentation/core-tutorial.txt @@ -184,7 +184,7 @@ $ git-cat-file -t 557db03de997c86a4a028e1ebd3a1ceb225be238 ---------------- where the `-t` tells `git-cat-file` to tell you what the "type" of the -object is. git will tell you that you have a "blob" object (ie just a +object is. git will tell you that you have a "blob" object (i.e., just a regular file), and you can see the contents with ---------------- @@ -619,7 +619,7 @@ $ git tag -s <tagname> ---------------- which will sign the current `HEAD` (but you can also give it another -argument that specifies the thing to tag, ie you could have tagged the +argument that specifies the thing to tag, i.e., you could have tagged the current `mybranch` point by using `git tag <tagname> mybranch`). You normally only do signed tags for major releases or things @@ -1097,7 +1097,7 @@ commit object by downloading from `repo.git/objects/xx/xxx\...` using the object name of that commit object. Then it reads the commit object to find out its parent commits and the associate tree object; it repeats this process until it gets all the -necessary objects. Because of this behaviour, they are +necessary objects. Because of this behavior, they are sometimes also called 'commit walkers'. + The 'commit walkers' are sometimes also called 'dumb |