padding-left: 0.5em;\r
}\r
</style>\r
-<title>A short git tutorial</title>\r
+<title>A git core tutorial for developers</title>\r
</head>\r
<body>\r
<div id="header">\r
-<h1>A short git tutorial</h1>\r
+<h1>A git core tutorial for developers</h1>\r
</div>\r
<h2>Introduction</h2>\r
<div class="sectionbody">\r
<pre><tt>$ git-cat-file -t 557db03de997c86a4a028e1ebd3a1ceb225be238</tt></pre>\r
</div></div>\r
<p>where the <tt>-t</tt> tells <tt>git-cat-file</tt> to tell you what the "type" of the\r
-object is. git will tell you that you have a "blob" object (ie just a\r
+object is. git will tell you that you have a "blob" object (i.e., just a\r
regular file), and you can see the contents with</p>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>$ git tag -s <tagname></tt></pre>\r
</div></div>\r
<p>which will sign the current <tt>HEAD</tt> (but you can also give it another\r
-argument that specifies the thing to tag, ie you could have tagged the\r
+argument that specifies the thing to tag, i.e., you could have tagged the\r
current <tt>mybranch</tt> point by using <tt>git tag <tagname> mybranch</tt>).</p>\r
<p>You normally only do signed tags for major releases or things\r
like that, while the light-weight tags are useful for any marking you\r
<p>The first two lines indicate that it is showing the two branches\r
and the first line of the commit log message from their\r
top-of-the-tree commits, you are currently on <tt>master</tt> branch\r
-(notice the asterisk <tt><strong></tt> character), and the first column for\r
+(notice the asterisk <tt>*</tt> character), and the first column for\r
the later output lines is used to show commits contained in the\r
<tt>master</tt> branch, and the second column for the <tt>mybranch</tt>\r
branch. Three commits are shown along with their log messages.\r
-All of them have non blank characters in the first column (<tt></strong></tt>\r
+All of them have non blank characters in the first column (<tt>*</tt>\r
shows an ordinary commit on the current branch, <tt>.</tt> is a merge commit), which\r
means they are now part of the <tt>master</tt> branch. Only the "Some\r
work" commit has the plus <tt>+</tt> character in the second column,\r
using the object name of that commit object. Then it reads the\r
commit object to find out its parent commits and the associate\r
tree object; it repeats this process until it gets all the\r
-necessary objects. Because of this behaviour, they are\r
+necessary objects. Because of this behavior, they are\r
sometimes also called <em>commit walkers</em>.</p>\r
<p>The <em>commit walkers</em> are sometimes also called <em>dumb\r
transports</em>, because they do not require any git aware smart\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Feb-2006 08:04:34 UTC\r
+Last updated 04-Jun-2006 07:24:36 UTC\r
</div>\r
</div>\r
</body>\r