git-rev-list.html - external/gitster/git-htmldocs - Git at Google

 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
  "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
 <meta name="generator" content="AsciiDoc 7.0.1" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
 /*
  border: 1px solid red;
 */
 }

 body {
  margin: 1em 5% 1em 5%;
 }

 a { color: blue; }
 a:visited { color: fuchsia; }

 em {
  font-style: italic;
 }

 strong {
  font-weight: bold;
 }

 tt {
  color: navy;
 }

 h1, h2, h3, h4, h5, h6 {
  color: #527bbd;
  font-family: sans-serif;
  margin-top: 1.2em;
  margin-bottom: 0.5em;
  line-height: 1.3;
 }

 h1 {
  border-bottom: 2px solid silver;
 }
 h2 {
  border-bottom: 2px solid silver;
  padding-top: 0.5em;
 }

 div.sectionbody {
  font-family: serif;
  margin-left: 0;
 }

 hr {
  border: 1px solid silver;
 }

 p {
  margin-top: 0.5em;
  margin-bottom: 0.5em;
 }

 pre {
  padding: 0;
  margin: 0;
 }

 span#author {
  color: #527bbd;
  font-family: sans-serif;
  font-weight: bold;
  font-size: 1.2em;
 }
 span#email {
 }
 span#revision {
  font-family: sans-serif;
 }

 div#footer {
  font-family: sans-serif;
  font-size: small;
  border-top: 2px solid silver;
  padding-top: 0.5em;
  margin-top: 4.0em;
 }
 div#footer-text {
  float: left;
  padding-bottom: 0.5em;
 }
 div#footer-badges {
  float: right;
  padding-bottom: 0.5em;
 }

 div#preamble,
 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 div.admonitionblock {
  margin-right: 10%;
  margin-top: 1.5em;
  margin-bottom: 1.5em;
 }
 div.admonitionblock {
  margin-top: 2.5em;
  margin-bottom: 2.5em;
 }

 div.content { /* Block element content. */
  padding: 0;
 }

 /* Block element titles. */
 div.title, caption.title {
  font-family: sans-serif;
  font-weight: bold;
  text-align: left;
  margin-top: 1.0em;
  margin-bottom: 0.5em;
 }
 div.title + * {
  margin-top: 0;
 }

 td div.title:first-child {
  margin-top: 0.0em;
 }
 div.content div.title:first-child {
  margin-top: 0.0em;
 }
 div.content + div.title {
  margin-top: 0.0em;
 }

 div.sidebarblock > div.content {
  background: #ffffee;
  border: 1px solid silver;
  padding: 0.5em;
 }

 div.listingblock > div.content {
  border: 1px solid silver;
  background: #f4f4f4;
  padding: 0.5em;
 }

 div.quoteblock > div.content {
  padding-left: 2.0em;
 }
 div.quoteblock .attribution {
  text-align: right;
 }

 div.admonitionblock .icon {
  vertical-align: top;
  font-size: 1.1em;
  font-weight: bold;
  text-decoration: underline;
  color: #527bbd;
  padding-right: 0.5em;
 }
 div.admonitionblock td.content {
  padding-left: 0.5em;
  border-left: 2px solid silver;
 }

 div.exampleblock > div.content {
  border-left: 2px solid silver;
  padding: 0.5em;
 }

 div.verseblock div.content {
  white-space: pre;
 }

 div.imageblock div.content { padding-left: 0; }
 div.imageblock img { border: 1px solid silver; }
 span.image img { border-style: none; }

 dl {
  margin-top: 0.8em;
  margin-bottom: 0.8em;
 }
 dt {
  margin-top: 0.5em;
  margin-bottom: 0;
  font-style: italic;
 }
 dd > *:first-child {
  margin-top: 0;
 }

 ul, ol {
  list-style-position: outside;
 }
 ol.olist2 {
  list-style-type: lower-alpha;
 }

 div.tableblock > table {
  border-color: #527bbd;
  border-width: 3px;
 }
 thead {
  font-family: sans-serif;
  font-weight: bold;
 }
 tfoot {
  font-weight: bold;
 }

 div.hlist {
  margin-top: 0.8em;
  margin-bottom: 0.8em;
 }
 td.hlist1 {
  vertical-align: top;
  font-style: italic;
  padding-right: 0.8em;
 }
 td.hlist2 {
  vertical-align: top;
 }

 @media print {
  div#footer-badges { display: none; }
 }
 include::./stylesheets/xhtml11-manpage.css[]
 /* Workarounds for IE6's broken and incomplete CSS2. */

 div.sidebar-content {
  background: #ffffee;
  border: 1px solid silver;
  padding: 0.5em;
 }
 div.sidebar-title, div.image-title {
  font-family: sans-serif;
  font-weight: bold;
  margin-top: 0.0em;
  margin-bottom: 0.5em;
 }

 div.listingblock div.content {
  border: 1px solid silver;
  background: #f4f4f4;
  padding: 0.5em;
 }

 div.quoteblock-content {
  padding-left: 2.0em;
 }

 div.exampleblock-content {
  border-left: 2px solid silver;
  padding-left: 0.5em;
 }
 </style>
 <title>git-rev-list(1)</title>
 </head>
 <body>
 <div id="header">
 <h1>
 git-rev-list(1) Manual Page
 </h1>
 <h2>NAME</h2>
 <div class="sectionbody">
 <p>git-rev-list -
  Lists commit objects in reverse chronological order
 </p>
 </div>
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
 <div class="content"><em>git-rev-list</em> [ --max-count=number ]
  [ --max-age=timestamp ]
  [ --min-age=timestamp ]
  [ --sparse ]
  [ --no-merges ]
  [ --all ]
  [ [ --merge-order [ --show-breaks ] ] | [ --topo-order ] ]
  [ --parents ]
  [ --objects [ --unpacked ] ]
  [ --pretty | --header ]
  [ --bisect ]
  &lt;commit&gt;&#8230; [ -- &lt;paths&gt;&#8230; ]</div></div>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
 <p>Lists commit objects in reverse chronological order starting at the
 given commit(s), taking ancestry relationship into account. This is
 useful to produce human-readable log output.</p>
 <p>Commits which are stated with a preceding <em>^</em> cause listing to stop at
 that point. Their parents are implied. "git-rev-list foo bar ^baz" thus
 means "list all the commits which are included in <em>foo</em> and <em>bar</em>, but
 not in <em>baz</em>".</p>
 <p>A special notation &lt;commit1&gt;..&lt;commit2&gt; can be used as a
 short-hand for ^&lt;commit1&gt; &lt;commit2&gt;.</p>
 </div>
 <h2>OPTIONS</h2>
 <div class="sectionbody">
 <dl>
 <dt>
 --pretty
 </dt>
 <dd>
 <p>
  Print the contents of the commit changesets in human-readable form.
 </p>
 </dd>
 <dt>
 --header
 </dt>
 <dd>
 <p>
  Print the contents of the commit in raw-format; each
  record is separated with a NUL character.
 </p>
 </dd>
 <dt>
 --objects
 </dt>
 <dd>
 <p>
  Print the object IDs of any object referenced by the listed commits.
  <em>git-rev-list --objects foo ^bar</em> thus means "send me all object IDs
  which I need to download if I have the commit object <em>bar</em>, but
  not <em>foo</em>".
 </p>
 </dd>
 <dt>
 --unpacked
 </dt>
 <dd>
 <p>
  Only useful with <tt>--objects</tt>; print the object IDs that
  are not in packs.
 </p>
 </dd>
 <dt>
 --bisect
 </dt>
 <dd>
 <p>
  Limit output to the one commit object which is roughly halfway
  between the included and excluded commits. Thus, if <em>git-rev-list
  --bisect foo <sup>bar </sup>baz</em> outputs <em>midpoint</em>, the output
  of <em>git-rev-list foo ^midpoint</em> and <em>git-rev-list midpoint
  <sup>bar </sup>baz</em> would be of roughly the same length. Finding the change
  which introduces a regression is thus reduced to a binary search:
  repeatedly generate and test new 'midpoint's until the commit chain
  is of length one.
 </p>
 </dd>
 <dt>
 --max-count
 </dt>
 <dd>
 <p>
  Limit the number of commits output.
 </p>
 </dd>
 <dt>
 --max-age=timestamp, --min-age=timestamp
 </dt>
 <dd>
 <p>
  Limit the commits output to specified time range.
 </p>
 </dd>
 <dt>
 --sparse
 </dt>
 <dd>
 <p>
  When optional paths are given, the command outputs only
  the commits that changes at least one of them, and also
  ignores merges that do not touch the given paths. This
  flag makes the command output all eligible commits
  (still subject to count and age limitation), but apply
  merge simplification nevertheless.
 </p>
 </dd>
 <dt>
 --all
 </dt>
 <dd>
 <p>
  Pretend as if all the refs in <tt>$GIT_DIR/refs/</tt> are
  listed on the command line as &lt;commit&gt;.
 </p>
 </dd>
 <dt>
 --topo-order
 </dt>
 <dd>
 <p>
  By default, the commits are shown in reverse
  chronological order. This option makes them appear in
  topological order (i.e. descendant commits are shown
  before their parents).
 </p>
 </dd>
 <dt>
 --merge-order
 </dt>
 <dd>
 <p>
  When specified the commit history is decomposed into a unique
  sequence of minimal, non-linear epochs and maximal, linear epochs.
  Non-linear epochs are then linearised by sorting them into merge
  order, which is described below.
 </p>
 <p>Maximal, linear epochs correspond to periods of sequential development.
 Minimal, non-linear epochs correspond to periods of divergent development
 followed by a converging merge. The theory of epochs is described in more
 detail at
 <a href="http://blackcubes.dyndns.org/epoch/">http://blackcubes.dyndns.org/epoch/</a>.</p>
 <p>The merge order for a non-linear epoch is defined as a linearisation for which
 the following invariants are true:</p>
 <ol>
 <li>
 <p>
 if a commit P is reachable from commit N, commit P sorts after commit N
  in the linearised list.
 </p>
 </li>
 <li>
 <p>
 if Pi and Pj are any two parents of a merge M (with i &lt; j), then any
  commit N, such that N is reachable from Pj but not reachable from Pi,
  sorts before all commits reachable from Pi.
 </p>
 <p>Invariant 1 states that later commits appear before earlier commits they are
 derived from.</p>
 <p>Invariant 2 states that commits unique to "later" parents in a merge, appear
 before all commits from "earlier" parents of a merge.</p>
 </li>
 </ol>
 </dd>
 <dt>
 --show-breaks
 </dt>
 <dd>
 <p>
  Each item of the list is output with a 2-character prefix consisting
  of one of: (|), (^), (=) followed by a space.
 </p>
 <p>Commits marked with (=) represent the boundaries of minimal, non-linear epochs
 and correspond either to the start of a period of divergent development or to
 the end of such a period.</p>
 <p>Commits marked with (|) are direct parents of commits immediately preceding
 the marked commit in the list.</p>
 <p>Commits marked with (^) are not parents of the immediately preceding commit.
 These "breaks" represent necessary discontinuities implied by trying to
 represent an arbitrary DAG in a linear form.</p>
 <p><tt>--show-breaks</tt> is only valid if <tt>--merge-order</tt> is also specified.</p>
 </dd>
 </dl>
 </div>
 <h2>Author</h2>
 <div class="sectionbody">
 <p>Written by Linus Torvalds &lt;torvalds@osdl.org&gt;</p>
 <p>Original <strong>--merge-order</strong> logic by Jon Seymour &lt;jon.seymour@gmail.com&gt;</p>
 </div>
 <h2>Documentation</h2>
 <div class="sectionbody">
 <p>Documentation by David Greaves, Junio C Hamano and the git-list &lt;git@vger.kernel.org&gt;.</p>
 </div>
 <h2>GIT</h2>
 <div class="sectionbody">
 <p>Part of the <a href="git.html">git(7)</a> suite</p>
 </div>
 <div id="footer">
 <div id="footer-text">
 Last updated 06-Jan-2006 17:12:43 PDT
 </div>
 </div>
 </body>
 </html>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
	"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
	<meta name="generator" content="AsciiDoc 7.0.1" />
	<style type="text/css">
	/* Debug borders */
	p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
	/*
	border: 1px solid red;
	*/
	}

	body {
	margin: 1em 5% 1em 5%;
	}

	a { color: blue; }
	a:visited { color: fuchsia; }

	em {
	font-style: italic;
	}

	strong {
	font-weight: bold;
	}

	tt {
	color: navy;
	}

	h1, h2, h3, h4, h5, h6 {
	color: #527bbd;
	font-family: sans-serif;
	margin-top: 1.2em;
	margin-bottom: 0.5em;
	line-height: 1.3;
	}

	h1 {
	border-bottom: 2px solid silver;
	}
	h2 {
	border-bottom: 2px solid silver;
	padding-top: 0.5em;
	}

	div.sectionbody {
	font-family: serif;
	margin-left: 0;
	}

	hr {
	border: 1px solid silver;
	}

	p {
	margin-top: 0.5em;
	margin-bottom: 0.5em;
	}

	pre {
	padding: 0;
	margin: 0;
	}

	span#author {
	color: #527bbd;
	font-family: sans-serif;
	font-weight: bold;
	font-size: 1.2em;
	}
	span#email {
	}
	span#revision {
	font-family: sans-serif;
	}

	div#footer {
	font-family: sans-serif;
	font-size: small;
	border-top: 2px solid silver;
	padding-top: 0.5em;
	margin-top: 4.0em;
	}
	div#footer-text {
	float: left;
	padding-bottom: 0.5em;
	}
	div#footer-badges {
	float: right;
	padding-bottom: 0.5em;
	}

	div#preamble,
	div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
	div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
	div.admonitionblock {
	margin-right: 10%;
	margin-top: 1.5em;
	margin-bottom: 1.5em;
	}
	div.admonitionblock {
	margin-top: 2.5em;
	margin-bottom: 2.5em;
	}

	div.content { /* Block element content. */
	padding: 0;
	}

	/* Block element titles. */
	div.title, caption.title {
	font-family: sans-serif;
	font-weight: bold;
	text-align: left;
	margin-top: 1.0em;
	margin-bottom: 0.5em;
	}
	div.title + * {
	margin-top: 0;
	}

	td div.title:first-child {
	margin-top: 0.0em;
	}
	div.content div.title:first-child {
	margin-top: 0.0em;
	}
	div.content + div.title {
	margin-top: 0.0em;
	}

	div.sidebarblock > div.content {
	background: #ffffee;
	border: 1px solid silver;
	padding: 0.5em;
	}

	div.listingblock > div.content {
	border: 1px solid silver;
	background: #f4f4f4;
	padding: 0.5em;
	}

	div.quoteblock > div.content {
	padding-left: 2.0em;
	}
	div.quoteblock .attribution {
	text-align: right;
	}

	div.admonitionblock .icon {
	vertical-align: top;
	font-size: 1.1em;
	font-weight: bold;
	text-decoration: underline;
	color: #527bbd;
	padding-right: 0.5em;
	}
	div.admonitionblock td.content {
	padding-left: 0.5em;
	border-left: 2px solid silver;
	}

	div.exampleblock > div.content {
	border-left: 2px solid silver;
	padding: 0.5em;
	}

	div.verseblock div.content {
	white-space: pre;
	}

	div.imageblock div.content { padding-left: 0; }
	div.imageblock img { border: 1px solid silver; }
	span.image img { border-style: none; }

	dl {
	margin-top: 0.8em;
	margin-bottom: 0.8em;
	}
	dt {
	margin-top: 0.5em;
	margin-bottom: 0;
	font-style: italic;
	}
	dd > *:first-child {
	margin-top: 0;
	}

	ul, ol {
	list-style-position: outside;
	}
	ol.olist2 {
	list-style-type: lower-alpha;
	}

	div.tableblock > table {
	border-color: #527bbd;
	border-width: 3px;
	}
	thead {
	font-family: sans-serif;
	font-weight: bold;
	}
	tfoot {
	font-weight: bold;
	}

	div.hlist {
	margin-top: 0.8em;
	margin-bottom: 0.8em;
	}
	td.hlist1 {
	vertical-align: top;
	font-style: italic;
	padding-right: 0.8em;
	}
	td.hlist2 {
	vertical-align: top;
	}

	@media print {
	div#footer-badges { display: none; }
	}
	include::./stylesheets/xhtml11-manpage.css[]
	/* Workarounds for IE6's broken and incomplete CSS2. */

	div.sidebar-content {
	background: #ffffee;
	border: 1px solid silver;
	padding: 0.5em;
	}
	div.sidebar-title, div.image-title {
	font-family: sans-serif;
	font-weight: bold;
	margin-top: 0.0em;
	margin-bottom: 0.5em;
	}

	div.listingblock div.content {
	border: 1px solid silver;
	background: #f4f4f4;
	padding: 0.5em;
	}

	div.quoteblock-content {
	padding-left: 2.0em;
	}

	div.exampleblock-content {
	border-left: 2px solid silver;
	padding-left: 0.5em;
	}
	</style>
	<title>git-rev-list(1)</title>
	</head>
	<body>
	<div id="header">
	<h1>
	git-rev-list(1) Manual Page
	</h1>
	<h2>NAME</h2>
	<div class="sectionbody">
	<p>git-rev-list -
	Lists commit objects in reverse chronological order
	</p>
	</div>
	</div>
	<h2>SYNOPSIS</h2>
	<div class="sectionbody">
	<div class="verseblock">
	<div class="content"><em>git-rev-list</em> [ --max-count=number ]
	[ --max-age=timestamp ]
	[ --min-age=timestamp ]
	[ --sparse ]
	[ --no-merges ]
	[ --all ]
	[ [ --merge-order [ --show-breaks ] ] \| [ --topo-order ] ]
	[ --parents ]
	[ --objects [ --unpacked ] ]
	[ --pretty \| --header ]
	[ --bisect ]
	<commit>… [ -- <paths>… ]</div></div>
	</div>
	<h2>DESCRIPTION</h2>
	<div class="sectionbody">
	<p>Lists commit objects in reverse chronological order starting at the
	given commit(s), taking ancestry relationship into account. This is
	useful to produce human-readable log output.</p>
	<p>Commits which are stated with a preceding <em>^</em> cause listing to stop at
	that point. Their parents are implied. "git-rev-list foo bar ^baz" thus
	means "list all the commits which are included in <em>foo</em> and <em>bar</em>, but
	not in <em>baz</em>".</p>
	<p>A special notation <commit1>..<commit2> can be used as a
	short-hand for ^<commit1> <commit2>.</p>
	</div>
	<h2>OPTIONS</h2>
	<div class="sectionbody">
	<dl>
	<dt>
	--pretty
	</dt>
	<dd>
	<p>
	Print the contents of the commit changesets in human-readable form.
	</p>
	</dd>
	<dt>
	--header
	</dt>
	<dd>
	<p>
	Print the contents of the commit in raw-format; each
	record is separated with a NUL character.
	</p>
	</dd>
	<dt>
	--objects
	</dt>
	<dd>
	<p>
	Print the object IDs of any object referenced by the listed commits.
	<em>git-rev-list --objects foo ^bar</em> thus means "send me all object IDs
	which I need to download if I have the commit object <em>bar</em>, but
	not <em>foo</em>".
	</p>
	</dd>
	<dt>
	--unpacked
	</dt>
	<dd>
	<p>
	Only useful with <tt>--objects</tt>; print the object IDs that
	are not in packs.
	</p>
	</dd>
	<dt>
	--bisect
	</dt>
	<dd>
	<p>
	Limit output to the one commit object which is roughly halfway
	between the included and excluded commits. Thus, if <em>git-rev-list
	--bisect foo <sup>bar </sup>baz</em> outputs <em>midpoint</em>, the output
	of <em>git-rev-list foo ^midpoint</em> and <em>git-rev-list midpoint
	<sup>bar </sup>baz</em> would be of roughly the same length. Finding the change
	which introduces a regression is thus reduced to a binary search:
	repeatedly generate and test new 'midpoint's until the commit chain
	is of length one.
	</p>
	</dd>
	<dt>
	--max-count
	</dt>
	<dd>
	<p>
	Limit the number of commits output.
	</p>
	</dd>
	<dt>
	--max-age=timestamp, --min-age=timestamp
	</dt>
	<dd>
	<p>
	Limit the commits output to specified time range.
	</p>
	</dd>
	<dt>
	--sparse
	</dt>
	<dd>
	<p>
	When optional paths are given, the command outputs only
	the commits that changes at least one of them, and also
	ignores merges that do not touch the given paths. This
	flag makes the command output all eligible commits
	(still subject to count and age limitation), but apply
	merge simplification nevertheless.
	</p>
	</dd>
	<dt>
	--all
	</dt>
	<dd>
	<p>
	Pretend as if all the refs in <tt>$GIT_DIR/refs/</tt> are
	listed on the command line as <commit>.
	</p>
	</dd>
	<dt>
	--topo-order
	</dt>
	<dd>
	<p>
	By default, the commits are shown in reverse
	chronological order. This option makes them appear in
	topological order (i.e. descendant commits are shown
	before their parents).
	</p>
	</dd>
	<dt>
	--merge-order
	</dt>
	<dd>
	<p>
	When specified the commit history is decomposed into a unique
	sequence of minimal, non-linear epochs and maximal, linear epochs.
	Non-linear epochs are then linearised by sorting them into merge
	order, which is described below.
	</p>
	<p>Maximal, linear epochs correspond to periods of sequential development.
	Minimal, non-linear epochs correspond to periods of divergent development
	followed by a converging merge. The theory of epochs is described in more
	detail at
	<a href="http://blackcubes.dyndns.org/epoch/">http://blackcubes.dyndns.org/epoch/</a>.</p>
	<p>The merge order for a non-linear epoch is defined as a linearisation for which
	the following invariants are true:</p>
	<ol>
	<li>
	<p>
	if a commit P is reachable from commit N, commit P sorts after commit N
	in the linearised list.
	</p>
	</li>
	<li>
	<p>
	if Pi and Pj are any two parents of a merge M (with i < j), then any
	commit N, such that N is reachable from Pj but not reachable from Pi,
	sorts before all commits reachable from Pi.
	</p>
	<p>Invariant 1 states that later commits appear before earlier commits they are
	derived from.</p>
	<p>Invariant 2 states that commits unique to "later" parents in a merge, appear
	before all commits from "earlier" parents of a merge.</p>
	</li>
	</ol>
	</dd>
	<dt>
	--show-breaks
	</dt>
	<dd>
	<p>
	Each item of the list is output with a 2-character prefix consisting
	of one of: (\|), (^), (=) followed by a space.
	</p>
	<p>Commits marked with (=) represent the boundaries of minimal, non-linear epochs
	and correspond either to the start of a period of divergent development or to
	the end of such a period.</p>
	<p>Commits marked with (\|) are direct parents of commits immediately preceding
	the marked commit in the list.</p>
	<p>Commits marked with (^) are not parents of the immediately preceding commit.
	These "breaks" represent necessary discontinuities implied by trying to
	represent an arbitrary DAG in a linear form.</p>
	<p><tt>--show-breaks</tt> is only valid if <tt>--merge-order</tt> is also specified.</p>
	</dd>
	</dl>
	</div>
	<h2>Author</h2>
	<div class="sectionbody">
	<p>Written by Linus Torvalds <torvalds@osdl.org></p>
	<p>Original <strong>--merge-order</strong> logic by Jon Seymour <jon.seymour@gmail.com></p>
	</div>
	<h2>Documentation</h2>
	<div class="sectionbody">
	<p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
	</div>
	<h2>GIT</h2>
	<div class="sectionbody">
	<p>Part of the <a href="git.html">git(7)</a> suite</p>
	</div>
	<div id="footer">
	<div id="footer-text">
	Last updated 06-Jan-2006 17:12:43 PDT
	</div>
	</div>
	</body>
	</html>