<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
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 30-May-2006 07:20:51 UTC\r
+Last updated 04-Jun-2006 07:24:36 UTC\r
</div>\r
</div>\r
</body>\r