X-Git-Url: https://git.verplant.org/?a=blobdiff_plain;ds=sidebyside;f=core-tutorial.html;h=7250064d4a369a4df8a486222659ed381ad6980f;hb=f0a85daaf3d624dcf841cad8d5d243e6da55ea70;hp=9dfa534f45f6e19a8c4456440760de929fdeff9e;hpb=40f2f8dd79c1622a7986e2ff2faa15c72860c79f;p=git.git diff --git a/core-tutorial.html b/core-tutorial.html index 9dfa534f..7250064d 100644 --- a/core-tutorial.html +++ b/core-tutorial.html @@ -255,11 +255,11 @@ div.exampleblock-content { padding-left: 0.5em; } -A short git tutorial +A git core tutorial for developers

Introduction

@@ -456,7 +456,7 @@ you'll have to use the object name, not the filename of the object:

$ 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

@@ -866,7 +866,7 @@ that tag. You create these annotated tags with either the -a or 
$ 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 like that, while the light-weight tags are useful for any marking you @@ -1186,11 +1186,11 @@ environment, is git show-branch.

The first two lines indicate that it is showing the two branches and the first line of the commit log message from their top-of-the-tree commits, you are currently on master branch -(notice the asterisk character), and the first column for +(notice the asterisk * character), and the first column for the later output lines is used to show commits contained in the master branch, and the second column for the mybranch branch. Three commits are shown along with their log messages. -All of them have non blank characters in the first column ( +All of them have non blank characters in the first column (* shows an ordinary commit on the current branch, . is a merge commit), which means they are now part of the master branch. Only the "Some work" commit has the plus + character in the second column, @@ -1323,7 +1323,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 transports, because they do not require any git aware smart @@ -2011,7 +2011,7 @@ to follow, not easier.