diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
| commit | ba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch) | |
| tree | 390507328a7564b65dc803683c34235700b97409 /githooks.html | |
| parent | 05bf9c54a827e48b2b576488f5170a3490b5180e (diff) | |
| download | git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz | |
Autogenerated HTML docs for v1.5.6.2-212-g08b5
Diffstat (limited to 'githooks.html')
| -rw-r--r-- | githooks.html | 352 |
1 files changed, 200 insertions, 152 deletions
diff --git a/githooks.html b/githooks.html index f130c11a8..6be1cdaf3 100644 --- a/githooks.html +++ b/githooks.html @@ -3,7 +3,7 @@ <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.2" />
+<meta name="generator" content="AsciiDoc 8.2.5" />
<style type="text/css">
/* Debug borders */
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -16,8 +16,13 @@ body { margin: 1em 5% 1em 5%;
}
-a { color: blue; }
-a:visited { color: fuchsia; }
+a {
+ color: blue;
+ text-decoration: underline;
+}
+a:visited {
+ color: fuchsia;
+}
em {
font-style: italic;
@@ -39,13 +44,18 @@ h1, h2, h3, h4, h5, h6 { line-height: 1.3;
}
-h1 {
+h1, h2, h3 {
border-bottom: 2px solid silver;
}
h2 {
- border-bottom: 2px solid silver;
padding-top: 0.5em;
}
+h3 {
+ float: left;
+}
+h3 + * {
+ clear: left;
+}
div.sectionbody {
font-family: serif;
@@ -70,7 +80,7 @@ span#author { color: #527bbd;
font-family: sans-serif;
font-weight: bold;
- font-size: 1.2em;
+ font-size: 1.1em;
}
span#email {
}
@@ -139,6 +149,9 @@ div.sidebarblock > div.content { padding: 0.5em;
}
+div.listingblock {
+ margin-right: 0%;
+}
div.listingblock > div.content {
border: 1px solid silver;
background: #f4f4f4;
@@ -148,9 +161,13 @@ div.listingblock > div.content { div.quoteblock > div.content {
padding-left: 2.0em;
}
-div.quoteblock .attribution {
+
+div.attribution {
text-align: right;
}
+div.verseblock + div.attribution {
+ text-align: left;
+}
div.admonitionblock .icon {
vertical-align: top;
@@ -194,13 +211,12 @@ dd > *:first-child { ul, ol {
list-style-position: outside;
}
-ol.olist2 {
+div.olist2 ol {
list-style-type: lower-alpha;
}
div.tableblock > table {
- border-color: #527bbd;
- border-width: 3px;
+ border: 3px solid #527bbd;
}
thead {
font-family: sans-serif;
@@ -214,6 +230,9 @@ div.hlist { margin-top: 0.8em;
margin-bottom: 0.8em;
}
+div.hlist td {
+ padding-bottom: 5px;
+}
td.hlist1 {
vertical-align: top;
font-style: italic;
@@ -226,7 +245,33 @@ td.hlist2 { @media print {
div#footer-badges { display: none; }
}
-include::./stylesheets/xhtml11-manpage.css[]
+
+div#toctitle {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 1.0em;
+ margin-bottom: 0.1em;
+}
+
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+div.toclevel2 {
+ margin-left: 2em;
+ font-size: 0.9em;
+}
+div.toclevel3 {
+ margin-left: 4em;
+ font-size: 0.9em;
+}
+div.toclevel4 {
+ margin-left: 6em;
+ font-size: 0.9em;
+}
+include1::./stylesheets/xhtml11-manpage.css[]
/* Workarounds for IE6's broken and incomplete CSS2. */
div.sidebar-content {
@@ -255,6 +300,9 @@ div.exampleblock-content { border-left: 2px solid silver;
padding-left: 0.5em;
}
+
+/* IE6 sets dynamically generated links as visited. */
+div#toc a:visited { color: blue; }
</style>
<title>githooks(5)</title>
</head>
@@ -272,163 +320,163 @@ githooks(5) Manual Page </div>
<h2>SYNOPSIS</h2>
<div class="sectionbody">
-<p>$GIT_DIR/hooks/*</p>
+<div class="para"><p>$GIT_DIR/hooks/*</p></div>
</div>
-<h2>DESCRIPTION</h2>
+<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<p>Hooks are little scripts you can place in <tt>$GIT_DIR/hooks</tt>
+<div class="para"><p>Hooks are little scripts you can place in <tt>$GIT_DIR/hooks</tt>
directory to trigger action at certain points. When
-<tt>git-init</tt> is run, a handful example hooks are copied in the
+<em>git-init</em> is run, a handful example hooks are copied in the
<tt>hooks</tt> directory of the new repository, but by default they are
all disabled. To enable a hook, rename it by removing its <tt>.sample</tt>
-suffix.</p>
-<p>This document describes the currently defined hooks.</p>
+suffix.</p></div>
+<div class="para"><p>This document describes the currently defined hooks.</p></div>
</div>
-<h2>applypatch-msg</h2>
+<h2 id="_applypatch_msg">applypatch-msg</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-am</tt> script. It takes a single
+<div class="para"><p>This hook is invoked by <em>git-am</em> script. It takes a single
parameter, the name of the file that holds the proposed commit
log message. Exiting with non-zero status causes
-<tt>git-am</tt> to abort before applying the patch.</p>
-<p>The hook is allowed to edit the message file in place, and can
+<em>git-am</em> to abort before applying the patch.</p></div>
+<div class="para"><p>The hook is allowed to edit the message file in place, and can
be used to normalize the message into some project standard
format (if the project has one). It can also be used to refuse
-the commit after inspecting the message file.</p>
-<p>The default <em>applypatch-msg</em> hook, when enabled, runs the
-<em>commit-msg</em> hook, if the latter is enabled.</p>
+the commit after inspecting the message file.</p></div>
+<div class="para"><p>The default <em>applypatch-msg</em> hook, when enabled, runs the
+<em>commit-msg</em> hook, if the latter is enabled.</p></div>
</div>
-<h2>pre-applypatch</h2>
+<h2 id="_pre_applypatch">pre-applypatch</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-am</tt>. It takes no parameter, and is
-invoked after the patch is applied, but before a commit is made.</p>
-<p>If it exits with non-zero status, then the working tree will not be
-committed after applying the patch.</p>
-<p>It can be used to inspect the current working tree and refuse to
-make a commit if it does not pass certain test.</p>
-<p>The default <em>pre-applypatch</em> hook, when enabled, runs the
-<em>pre-commit</em> hook, if the latter is enabled.</p>
+<div class="para"><p>This hook is invoked by <em>git-am</em>. It takes no parameter, and is
+invoked after the patch is applied, but before a commit is made.</p></div>
+<div class="para"><p>If it exits with non-zero status, then the working tree will not be
+committed after applying the patch.</p></div>
+<div class="para"><p>It can be used to inspect the current working tree and refuse to
+make a commit if it does not pass certain test.</p></div>
+<div class="para"><p>The default <em>pre-applypatch</em> hook, when enabled, runs the
+<em>pre-commit</em> hook, if the latter is enabled.</p></div>
</div>
-<h2>post-applypatch</h2>
+<h2 id="_post_applypatch">post-applypatch</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-am</tt>. It takes no parameter,
-and is invoked after the patch is applied and a commit is made.</p>
-<p>This hook is meant primarily for notification, and cannot affect
-the outcome of <tt>git-am</tt>.</p>
+<div class="para"><p>This hook is invoked by <em>git-am</em>. It takes no parameter,
+and is invoked after the patch is applied and a commit is made.</p></div>
+<div class="para"><p>This hook is meant primarily for notification, and cannot affect
+the outcome of <em>git-am</em>.</p></div>
</div>
-<h2>pre-commit</h2>
+<h2 id="_pre_commit">pre-commit</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-commit</tt>, and can be bypassed
+<div class="para"><p>This hook is invoked by <em>git-commit</em>, and can be bypassed
with <tt>--no-verify</tt> option. It takes no parameter, and is
invoked before obtaining the proposed commit log message and
making a commit. Exiting with non-zero status from this script
-causes the <tt>git-commit</tt> to abort.</p>
-<p>The default <em>pre-commit</em> hook, when enabled, catches introduction
+causes the <em>git-commit</em> to abort.</p></div>
+<div class="para"><p>The default <em>pre-commit</em> hook, when enabled, catches introduction
of lines with trailing whitespaces and aborts the commit when
-such a line is found.</p>
-<p>All the <tt>git-commit</tt> hooks are invoked with the environment
+such a line is found.</p></div>
+<div class="para"><p>All the <em>git-commit</em> hooks are invoked with the environment
variable <tt>GIT_EDITOR=:</tt> if the command will not bring up an editor
-to modify the commit message.</p>
+to modify the commit message.</p></div>
</div>
-<h2>prepare-commit-msg</h2>
+<h2 id="_prepare_commit_msg">prepare-commit-msg</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-commit</tt> right after preparing the
-default log message, and before the editor is started.</p>
-<p>It takes one to three parameters. The first is the name of the file
+<div class="para"><p>This hook is invoked by <em>git-commit</em> right after preparing the
+default log message, and before the editor is started.</p></div>
+<div class="para"><p>It takes one to three parameters. The first is the name of the file
that the commit log message. The second is the source of the commit
message, and can be: <tt>message</tt> (if a <tt>\-m</tt> or <tt>\-F</tt> option was
given); <tt>template</tt> (if a <tt>\-t</tt> option was given or the
configuration option <tt>commit.template</tt> is set); <tt>merge</tt> (if the
commit is a merge or a <tt>.git/MERGE_MSG</tt> file exists); <tt>squash</tt>
(if a <tt>.git/SQUASH_MSG</tt> file exists); or <tt>commit</tt>, followed by
-a commit SHA1 (if a <tt>\-c</tt>, <tt>\-C</tt> or <tt>--amend</tt> option was given).</p>
-<p>If the exit status is non-zero, <tt>git-commit</tt> will abort.</p>
-<p>The purpose of the hook is to edit the message file in place, and
+a commit SHA1 (if a <tt>\-c</tt>, <tt>\-C</tt> or <tt>--amend</tt> option was given).</p></div>
+<div class="para"><p>If the exit status is non-zero, <em>git-commit</em> will abort.</p></div>
+<div class="para"><p>The purpose of the hook is to edit the message file in place, and
it is not suppressed by the <tt>--no-verify</tt> option. A non-zero exit
means a failure of the hook and aborts the commit. It should not
-be used as replacement for pre-commit hook.</p>
-<p>The sample <tt>prepare-commit-msg</tt> hook that comes with git comments
-out the <tt>Conflicts:</tt> part of a merge's commit message.</p>
+be used as replacement for pre-commit hook.</p></div>
+<div class="para"><p>The sample <tt>prepare-commit-msg</tt> hook that comes with git comments
+out the <tt>Conflicts:</tt> part of a merge's commit message.</p></div>
</div>
-<h2>commit-msg</h2>
+<h2 id="_commit_msg">commit-msg</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-commit</tt>, and can be bypassed
+<div class="para"><p>This hook is invoked by <em>git-commit</em>, and can be bypassed
with <tt>--no-verify</tt> option. It takes a single parameter, the
name of the file that holds the proposed commit log message.
-Exiting with non-zero status causes the <tt>git-commit</tt> to
-abort.</p>
-<p>The hook is allowed to edit the message file in place, and can
+Exiting with non-zero status causes the <em>git-commit</em> to
+abort.</p></div>
+<div class="para"><p>The hook is allowed to edit the message file in place, and can
be used to normalize the message into some project standard
format (if the project has one). It can also be used to refuse
-the commit after inspecting the message file.</p>
-<p>The default <em>commit-msg</em> hook, when enabled, detects duplicate
-"Signed-off-by" lines, and aborts the commit if one is found.</p>
+the commit after inspecting the message file.</p></div>
+<div class="para"><p>The default <em>commit-msg</em> hook, when enabled, detects duplicate
+"Signed-off-by" lines, and aborts the commit if one is found.</p></div>
</div>
-<h2>post-commit</h2>
+<h2 id="_post_commit">post-commit</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-commit</tt>. It takes no
-parameter, and is invoked after a commit is made.</p>
-<p>This hook is meant primarily for notification, and cannot affect
-the outcome of <tt>git-commit</tt>.</p>
+<div class="para"><p>This hook is invoked by <em>git-commit</em>. It takes no
+parameter, and is invoked after a commit is made.</p></div>
+<div class="para"><p>This hook is meant primarily for notification, and cannot affect
+the outcome of <em>git-commit</em>.</p></div>
</div>
-<h2>post-checkout</h2>
+<h2 id="_post_checkout">post-checkout</h2>
<div class="sectionbody">
-<p>This hook is invoked when a <tt>git-checkout</tt> is run after having updated the
+<div class="para"><p>This hook is invoked when a <em>git-checkout</em> is run after having updated the
worktree. The hook is given three parameters: the ref of the previous HEAD,
the ref of the new HEAD (which may or may not have changed), and a flag
indicating whether the checkout was a branch checkout (changing branches,
flag=1) or a file checkout (retrieving a file from the index, flag=0).
-This hook cannot affect the outcome of <tt>git-checkout</tt>.</p>
-<p>This hook can be used to perform repository validity checks, auto-display
+This hook cannot affect the outcome of <em>git-checkout</em>.</p></div>
+<div class="para"><p>This hook can be used to perform repository validity checks, auto-display
differences from the previous HEAD if different, or set working dir metadata
-properties.</p>
+properties.</p></div>
</div>
-<h2>post-merge</h2>
+<h2 id="_post_merge">post-merge</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-merge</tt>, which happens when a <tt>git-pull</tt>
+<div class="para"><p>This hook is invoked by <em>git-merge</em>, which happens when a <em>git-pull</em>
is done on a local repository. The hook takes a single parameter, a status
flag specifying whether or not the merge being done was a squash merge.
-This hook cannot affect the outcome of <tt>git-merge</tt> and is not executed,
-if the merge failed due to conflicts.</p>
-<p>This hook can be used in conjunction with a corresponding pre-commit hook to
+This hook cannot affect the outcome of <em>git-merge</em> and is not executed,
+if the merge failed due to conflicts.</p></div>
+<div class="para"><p>This hook can be used in conjunction with a corresponding pre-commit hook to
save and restore any form of metadata associated with the working tree
(eg: permissions/ownership, ACLS, etc). See contrib/hooks/setgitperms.perl
-for an example of how to do this.</p>
+for an example of how to do this.</p></div>
</div>
-<h2><a id="pre-receive"></a>pre-receive</h2>
+<h2 id="pre-receive">pre-receive</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-receive-pack</tt> on the remote repository,
-which happens when a <tt>git-push</tt> is done on a local repository.
+<div class="para"><p>This hook is invoked by <em>git-receive-pack</em> on the remote repository,
+which happens when a <em>git-push</em> is done on a local repository.
Just before starting to update refs on the remote repository, the
pre-receive hook is invoked. Its exit status determines the success
-or failure of the update.</p>
-<p>This hook executes once for the receive operation. It takes no
+or failure of the update.</p></div>
+<div class="para"><p>This hook executes once for the receive operation. It takes no
arguments, but for each ref to be updated it receives on standard
-input a line of the format:</p>
+input a line of the format:</p></div>
<div class="literalblock">
<div class="content">
<pre><tt><old-value> SP <new-value> SP <ref-name> LF</tt></pre>
</div></div>
-<p>where <tt><old-value></tt> is the old object name stored in the ref,
+<div class="para"><p>where <tt><old-value></tt> is the old object name stored in the ref,
<tt><new-value></tt> is the new object name to be stored in the ref and
<tt><ref-name></tt> is the full name of the ref.
-When creating a new ref, <tt><old-value></tt> is 40 <tt>0</tt>.</p>
-<p>If the hook exits with non-zero status, none of the refs will be
+When creating a new ref, <tt><old-value></tt> is 40 <tt>0</tt>.</p></div>
+<div class="para"><p>If the hook exits with non-zero status, none of the refs will be
updated. If the hook exits with zero, updating of individual refs can
-still be prevented by the <a href="#update"><em>update</em></a> hook.</p>
-<p>Both standard output and standard error output are forwarded to
-<tt>git-send-pack</tt> on the other end, so you can simply <tt>echo</tt> messages
-for the user.</p>
+still be prevented by the <a href="#update"><em>update</em></a> hook.</p></div>
+<div class="para"><p>Both standard output and standard error output are forwarded to
+<em>git-send-pack</em> on the other end, so you can simply <tt>echo</tt> messages
+for the user.</p></div>
</div>
-<h2><a id="update"></a>update</h2>
+<h2 id="update">update</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-receive-pack</tt> on the remote repository,
-which happens when a <tt>git-push</tt> is done on a local repository.
+<div class="para"><p>This hook is invoked by <em>git-receive-pack</em> on the remote repository,
+which happens when a <em>git-push</em> is done on a local repository.
Just before updating the ref on the remote repository, the update hook
is invoked. Its exit status determines the success or failure of
-the ref update.</p>
-<p>The hook executes once for each ref to be updated, and takes
-three parameters:</p>
-<ul>
+the ref update.</p></div>
+<div class="para"><p>The hook executes once for each ref to be updated, and takes
+three parameters:</p></div>
+<div class="ilist"><ul>
<li>
<p>
the name of the ref being updated,
@@ -444,89 +492,89 @@ the old object name stored in the ref, and the new objectname to be stored in the ref.
</p>
</li>
-</ul>
-<p>A zero exit from the update hook allows the ref to be updated.
-Exiting with a non-zero status prevents <tt>git-receive-pack</tt>
-from updating that ref.</p>
-<p>This hook can be used to prevent <em>forced</em> update on certain refs by
+</ul></div>
+<div class="para"><p>A zero exit from the update hook allows the ref to be updated.
+Exiting with a non-zero status prevents <em>git-receive-pack</em>
+from updating that ref.</p></div>
+<div class="para"><p>This hook can be used to prevent <em>forced</em> update on certain refs by
making sure that the object name is a commit object that is a
descendant of the commit object named by the old object name.
-That is, to enforce a "fast forward only" policy.</p>
-<p>It could also be used to log the old..new status. However, it
+That is, to enforce a "fast forward only" policy.</p></div>
+<div class="para"><p>It could also be used to log the old..new status. However, it
does not know the entire set of branches, so it would end up
firing one e-mail per ref when used naively, though. The
-<a href="#post-receive"><em>post-receive</em></a> hook is more suited to that.</p>
-<p>Another use suggested on the mailing list is to use this hook to
+<a href="#post-receive"><em>post-receive</em></a> hook is more suited to that.</p></div>
+<div class="para"><p>Another use suggested on the mailing list is to use this hook to
implement access control which is finer grained than the one
-based on filesystem group.</p>
-<p>Both standard output and standard error output are forwarded to
-<tt>git-send-pack</tt> on the other end, so you can simply <tt>echo</tt> messages
-for the user.</p>
-<p>The default <em>update</em> hook, when enabled--and with
+based on filesystem group.</p></div>
+<div class="para"><p>Both standard output and standard error output are forwarded to
+<em>git-send-pack</em> on the other end, so you can simply <tt>echo</tt> messages
+for the user.</p></div>
+<div class="para"><p>The default <em>update</em> hook, when enabled--and with
<tt>hooks.allowunannotated</tt> config option turned on--prevents
-unannotated tags to be pushed.</p>
+unannotated tags to be pushed.</p></div>
</div>
-<h2><a id="post-receive"></a>post-receive</h2>
+<h2 id="post-receive">post-receive</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-receive-pack</tt> on the remote repository,
-which happens when a <tt>git-push</tt> is done on a local repository.
+<div class="para"><p>This hook is invoked by <em>git-receive-pack</em> on the remote repository,
+which happens when a <em>git-push</em> is done on a local repository.
It executes on the remote repository once after all the refs have
-been updated.</p>
-<p>This hook executes once for the receive operation. It takes no
+been updated.</p></div>
+<div class="para"><p>This hook executes once for the receive operation. It takes no
arguments, but gets the same information as the
<a href="#pre-receive"><em>pre-receive</em></a>
-hook does on its standard input.</p>
-<p>This hook does not affect the outcome of <tt>git-receive-pack</tt>, as it
-is called after the real work is done.</p>
-<p>This supersedes the <a href="#post-update"><em>post-update</em></a> hook in that it gets
+hook does on its standard input.</p></div>
+<div class="para"><p>This hook does not affect the outcome of <em>git-receive-pack</em>, as it
+is called after the real work is done.</p></div>
+<div class="para"><p>This supersedes the <a href="#post-update"><em>post-update</em></a> hook in that it gets
both old and new values of all the refs in addition to their
-names.</p>
-<p>Both standard output and standard error output are forwarded to
-<tt>git-send-pack</tt> on the other end, so you can simply <tt>echo</tt> messages
-for the user.</p>
-<p>The default <em>post-receive</em> hook is empty, but there is
+names.</p></div>
+<div class="para"><p>Both standard output and standard error output are forwarded to
+<em>git-send-pack</em> on the other end, so you can simply <tt>echo</tt> messages
+for the user.</p></div>
+<div class="para"><p>The default <em>post-receive</em> hook is empty, but there is
a sample script <tt>post-receive-email</tt> provided in the <tt>contrib/hooks</tt>
directory in git distribution, which implements sending commit
-emails.</p>
+emails.</p></div>
</div>
-<h2><a id="post-update"></a>post-update</h2>
+<h2 id="post-update">post-update</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-receive-pack</tt> on the remote repository,
-which happens when a <tt>git-push</tt> is done on a local repository.
+<div class="para"><p>This hook is invoked by <em>git-receive-pack</em> on the remote repository,
+which happens when a <em>git-push</em> is done on a local repository.
It executes on the remote repository once after all the refs have
-been updated.</p>
-<p>It takes a variable number of parameters, each of which is the
-name of ref that was actually updated.</p>
-<p>This hook is meant primarily for notification, and cannot affect
-the outcome of <tt>git-receive-pack</tt>.</p>
-<p>The <em>post-update</em> hook can tell what are the heads that were pushed,
+been updated.</p></div>
+<div class="para"><p>It takes a variable number of parameters, each of which is the
+name of ref that was actually updated.</p></div>
+<div class="para"><p>This hook is meant primarily for notification, and cannot affect
+the outcome of <em>git-receive-pack</em>.</p></div>
+<div class="para"><p>The <em>post-update</em> hook can tell what are the heads that were pushed,
but it does not know what their original and updated values are,
so it is a poor place to do log old..new. The
<a href="#post-receive"><em>post-receive</em></a> hook does get both original and
updated values of the refs. You might consider it instead if you need
-them.</p>
-<p>When enabled, the default <em>post-update</em> hook runs
-<tt>git-update-server-info</tt> to keep the information used by dumb
+them.</p></div>
+<div class="para"><p>When enabled, the default <em>post-update</em> hook runs
+<em>git-update-server-info</em> to keep the information used by dumb
transports (e.g., HTTP) up-to-date. If you are publishing
a git repository that is accessible via HTTP, you should
-probably enable this hook.</p>
-<p>Both standard output and standard error output are forwarded to
-<tt>git-send-pack</tt> on the other end, so you can simply <tt>echo</tt> messages
-for the user.</p>
+probably enable this hook.</p></div>
+<div class="para"><p>Both standard output and standard error output are forwarded to
+<em>git-send-pack</em> on the other end, so you can simply <tt>echo</tt> messages
+for the user.</p></div>
</div>
-<h2>pre-auto-gc</h2>
+<h2 id="_pre_auto_gc">pre-auto-gc</h2>
<div class="sectionbody">
-<p>This hook is invoked by <tt>git-gc --auto</tt>. It takes no parameter, and
-exiting with non-zero status from this script causes the <tt>git-gc --auto</tt>
-to abort.</p>
+<div class="para"><p>This hook is invoked by <em>git-gc --auto</em>. It takes no parameter, and
+exiting with non-zero status from this script causes the <em>git-gc --auto</em>
+to abort.</p></div>
</div>
-<h2>GIT</h2>
+<h2 id="_git">GIT</h2>
<div class="sectionbody">
-<p>Part of the <a href="git.html">git(1)</a> suite</p>
+<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 02-Jul-2008 03:02:10 UTC
+Last updated 2008-07-06 05:17:10 UTC
</div>
</div>
</body>
|