changeset 90:1d853842db62

Add an index with anchor tags to jump to sections.
author Rob Landley <rob@landley.net>
date Fri, 09 Nov 2007 19:56:05 -0600
parents ac8a8db09cd1
children 559603be1678
files local/git-quick.html
diffstat 1 files changed, 27 insertions(+), 12 deletions(-) [+]
line wrap: on
line diff
--- a/local/git-quick.html	Wed Nov 07 23:42:52 2007 -0600
+++ b/local/git-quick.html	Fri Nov 09 19:56:05 2007 -0600
@@ -1,6 +1,21 @@
 <title>Following Linux kernel development with git</title>
 
-<h2>A "git bisect HOWTO" with a few extras.</h2>
+<ul>
+<li><a href="#what">A "git bisect HOWTO" with a few extras.</a></li>
+<li><a href="#installing">Installing git</a></li>
+<li><a href="#downloading">Downloading the kernel with git</a></li>
+<li><a href="#updating">Updating your local copy</a></li>
+<li><a href="#looking">Looking at historical versions</a></li>
+<li><a href="#versions">Working with historical versions<a></li>
+<li><a href="#diff">Using git diff</a></li>
+<li><a href="#tarballs">Creating tarballs</a></li>
+<li><a href="#bisect">Bisect</a></li>
+<li><a href="#example">Example git bisect run</a></li>
+<li><a href="#commands">Command summary</a></li>
+<li><a href="#linus">Linus Tovalds talks about git</a></li>
+</ul>
+
+<a name="what><h2>A "git bisect HOWTO" with a few extras.</h2>
 
 <p>This document tells you how to follow Linux kernel development (and
 examine its history) with git.  It does not assume you've ever used a source
@@ -16,7 +31,7 @@
 larger tutorial</a> that explains concepts like "branches".  This one
 shouldn't get in the way of doing that sort of thing, but it doesn't go there.</p>
 
-<h2>Installing git</h2>
+<a name="installing"><h2>Installing git</h2>
 
 <p>First, install a recent version of git.  (Note that the user interface
 changed drastically in git-1.5.0, and this page only describes the new
@@ -32,7 +47,7 @@
 and extract it into /usr/share/man.  You want the man pages because "git help"
 displays them.</p>
 
-<h2>Downloading the kernel with git</h2>
+<a name="downloading"><h2>Downloading the kernel with git</h2>
 
 <p>The following command will download the current linux-kernel repository into
 a local directory called "linux-git":</p>
@@ -62,7 +77,7 @@
 ".git/FETCH_HEAD".  Normally you shouldn't need to care, since git remembers
 it.)</p>
 
-<h2>Updating your local copy</h2>
+<a name="updating"><h2>Updating your local copy</h2>
 
 <p>The command "<b>git pull</b>" downloads all the changes committed to Linus's
 git repository since the last time you updated your copy, and appends those
@@ -78,7 +93,7 @@
 with a very slow one) and still have access to the complete revision history
 you've already downloaded.</p>
 
-<h2>Looking at historical versions</h2>
+<a name="looking"><h2>Looking at historical versions</h2>
 
 <p>The <b>git log</b> command lists the changes recorded in your repository,
 starting with the most recent and working back.  The big hexadecimal numbers
@@ -101,7 +116,7 @@
 blame</b> is difficult to read on an 80 charater terminal, try <b>git blame
 $FILE | sed 's/(.*)//'</b> to see more of the file itself.)</p>
 
-<h2>Working with historical versions</h2>
+<a name="versions"><h2>Working with historical versions</h2>
 
 <p>The <b>git checkout</b> command changes your working copy of the source to a
 specific version.  The -f option to checkout backs out any local changes
@@ -128,7 +143,7 @@
 looking at, and <b>git log master</b> to compare against the most recent
 commits in the repository.</p>
 
-<h2>Using git diff</h2>
+<a name="diff"><h2>Using git diff</h2>
 
 <p>The command "git diff" shows differences between git versions.  You can
 ask it to show differences between:</p>
@@ -156,7 +171,7 @@
 behavior of removing all lines from one file and adding them to another.
 (This behavior may become the default in a future version.)</p>
 
-<h2>Creating tarballs</h2>
+<a name="tarballs"><h2>Creating tarballs</h2>
 
 <p>The <b>git archive $VERSION</b> command creates a tarball (written to
 stdout) of the given version.  Note that "master" isn't the default here,
@@ -189,7 +204,7 @@
 afterwards with <b>git checkout -f; git clean -d</b>.  (Better than
 "make distclean".)</p>
 
-<h2>Bisect</h2>
+<a name="bisect"><h2>Bisect</h2>
 
 <p>Possibly the most useful thing git does for non-kernel developers is
 <b>git bisect</b>, which can track down a bug to a specific revision.  This
@@ -248,7 +263,7 @@
 need to back up, the bisect log is an easily editable text file you can
 always chop a few lines off the end of.</p>
 
-<h2>Example git bisect run</h2>
+<a name="example"><h2>Example git bisect run</h2>
 
 <p>Here is a real git bisect run I did on the <a href=http://qemu.org>qemu</a>
 git repository (git://git.kernel.dk/data/git/qemu) to figure out why
@@ -348,7 +363,7 @@
 
 <p>
 
-<h2>Command summary</h2>
+<a name="commands"><h2>Command summary</h2>
 
 <p><b>git help</b></p> - List available commands.  You can also go
 <b>git help COMMANDNAME</b> to see help on a specific command.  Note,
@@ -398,7 +413,7 @@
 arguments after that are filenames.  Add "--find-copies-harder" to detect
 renames.</p>
 
-<h2>Linus Tovalds talks about git</h2>
+<a name="linus"><h2>Linus Tovalds talks about git</h2>
 
 <p>In <a href=http://youtube.com/watch?v=4XpnKHJAok8>this Google Tech Talk</a></p>