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
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-May-2006 23:36:13 UTC\r
+Last updated 30-May-2006 07:20:51 UTC\r
</div>\r
</div>\r
</body>\r
-A short git tutorial
-====================
+A git core tutorial for developers
+==================================
Introduction
------------
<li>\r
<p>\r
check how many loose objects there are and how much\r
-diskspace is wasted by not repacking.\r
+disk space is wasted by not repacking.\r
</p>\r
</li>\r
<li>\r
<h2>Individual Developer (Standalone)<a id="Individual Developer (Standalone)"></a></h2>\r
<div class="sectionbody">\r
<p>A standalone individual developer does not exchange patches with\r
-other poeple, and works alone in a single repository, using the\r
+other people, and works alone in a single repository, using the\r
following commands.</p>\r
<ul>\r
<li>\r
<dd>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>$ grep git /etc/inet.conf\r
+<pre><tt>$ grep git /etc/inetd.conf\r
git stream tcp nowait nobody \\r
/usr/bin/git-daemon git-daemon --inetd --syslog --export-all /pub/scm</tt></pre>\r
</div></div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Apr-2006 07:01:35 UTC\r
+Last updated 30-May-2006 07:20:54 UTC\r
</div>\r
</div>\r
</body>\r
<1> running without "--full" is usually cheap and assures the
repository health reasonably well.
<2> check how many loose objects there are and how much
-diskspace is wasted by not repacking.
+disk space is wasted by not repacking.
<3> without "-a" repacks incrementally. repacking every 4-5MB
of loose objects accumulation may be a good rule of thumb.
<4> after repack, prune removes the duplicate loose objects.
----------------------------------------------------------------------
A standalone individual developer does not exchange patches with
-other poeple, and works alone in a single repository, using the
+other people, and works alone in a single repository, using the
following commands.
* gitlink:git-show-branch[1] to see where you are.
Run git-daemon to serve /pub/scm from inetd.::
+
------------
-$ grep git /etc/inet.conf
+$ grep git /etc/inetd.conf
git stream tcp nowait nobody \
/usr/bin/git-daemon git-daemon --inetd --syslog --export-all /pub/scm
------------
pages for any of the git commands; one good place to start would be\r
with the commands mentioned in <a href="everyday.html">Everyday git</a>. You\r
should be able to find any unknown jargon in the\r
-<a href="glossary.html">Glosssay</a>.</p>\r
+<a href="glossary.html">Glossary</a>.</p>\r
<p>The <a href="cvs-migration.html">CVS migration</a> document explains how to\r
import a CVS repository into git, and shows how to use git in a\r
CVS-like way.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 22-May-2006 22:34:51 UTC\r
+Last updated 30-May-2006 07:20:51 UTC\r
</div>\r
</div>\r
</body>\r
pages for any of the git commands; one good place to start would be
with the commands mentioned in link:everyday.html[Everyday git]. You
should be able to find any unknown jargon in the
-link:glossary.html[Glosssay].
+link:glossary.html[Glossary].
The link:cvs-migration.html[CVS migration] document explains how to
import a CVS repository into git, and shows how to use git in a
<pre><tt>$ gitk --since="2 weeks ago" drivers/</tt></pre>\r
</div></div>\r
<p>allows you to browse any commits from the last 2 weeks of commits\r
-that modified files under the "drivers" directory.</p>\r
+that modified files under the "drivers" directory. (Note: you can\r
+adjust gitk's fonts by holding down the control key while pressing\r
+"-" or "+".)</p>\r
<p>Finally, most commands that take filenames will optionally allow you\r
to precede any filename by a commit, to specify a particular version\r
-fo the file:</p>\r
+of the file:</p>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>$ git diff v2.5:Makefile HEAD:Makefile.in</tt></pre>\r
</div></div>\r
+<p>You can also use "git cat-file -p" to see any such file:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ git cat-file -p v2.5:Makefile</tt></pre>\r
+</div></div>\r
</div>\r
<h2>Next Steps</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 22-May-2006 01:09:52 UTC\r
+Last updated 30-May-2006 07:20:50 UTC\r
</div>\r
</div>\r
</body>\r
-------------------------------------
allows you to browse any commits from the last 2 weeks of commits
-that modified files under the "drivers" directory.
+that modified files under the "drivers" directory. (Note: you can
+adjust gitk's fonts by holding down the control key while pressing
+"-" or "+".)
Finally, most commands that take filenames will optionally allow you
to precede any filename by a commit, to specify a particular version
-fo the file:
+of the file:
-------------------------------------
$ git diff v2.5:Makefile HEAD:Makefile.in
-------------------------------------
+You can also use "git cat-file -p" to see any such file:
+
+-------------------------------------
+$ git cat-file -p v2.5:Makefile
+-------------------------------------
+
Next Steps
----------
projects / git.git / commitdiff