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 /git-receive-pack.html | |
| parent | 05bf9c54a827e48b2b576488f5170a3490b5180e (diff) | |
| download | git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz | |
Autogenerated HTML docs for v1.5.6.2-212-g08b5
Diffstat (limited to 'git-receive-pack.html')
| -rw-r--r-- | git-receive-pack.html | 198 |
1 files changed, 123 insertions, 75 deletions
diff --git a/git-receive-pack.html b/git-receive-pack.html index d5ea89b57..d4c5cfb09 100644 --- a/git-receive-pack.html +++ b/git-receive-pack.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>git-receive-pack(1)</title>
</head>
@@ -272,29 +320,29 @@ git-receive-pack(1) Manual Page </div>
<h2>SYNOPSIS</h2>
<div class="sectionbody">
-<p><em>git receive-pack</em> <directory></p>
+<div class="para"><p><em>git receive-pack</em> <directory></p></div>
</div>
-<h2>DESCRIPTION</h2>
+<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<p>Invoked by <tt>git-send-pack</tt> and updates the repository with the
-information fed from the remote end.</p>
-<p>This command is usually not invoked directly by the end user.
-The UI for the protocol is on the <tt>git-send-pack</tt> side, and the
+<div class="para"><p>Invoked by <em>git-send-pack</em> and updates the repository with the
+information fed from the remote end.</p></div>
+<div class="para"><p>This command is usually not invoked directly by the end user.
+The UI for the protocol is on the <em>git-send-pack</em> side, and the
program pair is meant to be used to push updates to remote
-repository. For pull operations, see <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.</p>
-<p>The command allows for creation and fast forwarding of sha1 refs
+repository. For pull operations, see <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.</p></div>
+<div class="para"><p>The command allows for creation and fast forwarding of sha1 refs
(heads/tags) on the remote end (strictly speaking, it is the
-local end <tt>git-receive-pack</tt> runs, but to the user who is sitting at
-the send-pack end, it is updating the remote. Confused?)</p>
-<p>There are other real-world examples of using update and
-post-update hooks found in the Documentation/howto directory.</p>
-<p><tt>git-receive-pack</tt> honours the receive.denyNonFastForwards config
+local end <em>git-receive-pack</em> runs, but to the user who is sitting at
+the send-pack end, it is updating the remote. Confused?)</p></div>
+<div class="para"><p>There are other real-world examples of using update and
+post-update hooks found in the Documentation/howto directory.</p></div>
+<div class="para"><p><em>git-receive-pack</em> honours the receive.denyNonFastForwards config
option, which tells it if updates to a ref should be denied if they
-are not fast-forwards.</p>
+are not fast-forwards.</p></div>
</div>
-<h2>OPTIONS</h2>
+<h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
-<dl>
+<div class="vlist"><dl>
<dt>
<directory>
</dt>
@@ -303,72 +351,72 @@ are not fast-forwards.</p> The repository to sync into.
</p>
</dd>
-</dl>
+</dl></div>
</div>
-<h2>pre-receive Hook</h2>
+<h2 id="_pre_receive_hook">pre-receive Hook</h2>
<div class="sectionbody">
-<p>Before any ref is updated, if $GIT_DIR/hooks/pre-receive file exists
+<div class="para"><p>Before any ref is updated, if $GIT_DIR/hooks/pre-receive file exists
and is executable, it will be invoked once with no parameters. The
-standard input of the hook will be one line per ref to be updated:</p>
+standard input of the hook will be one line per ref to be updated:</p></div>
<div class="literalblock">
<div class="content">
<pre><tt>sha1-old SP sha1-new SP refname LF</tt></pre>
</div></div>
-<p>The refname value is relative to $GIT_DIR; e.g. for the master
+<div class="para"><p>The refname value is relative to $GIT_DIR; e.g. for the master
head this is "refs/heads/master". The two sha1 values before
each refname are the object names for the refname before and after
the update. Refs to be created will have sha1-old equal to 0{40},
while refs to be deleted will have sha1-new equal to 0{40}, otherwise
-sha1-old and sha1-new should be valid objects in the repository.</p>
-<p>This hook is called before any refname is updated and before any
-fast-forward checks are performed.</p>
-<p>If the pre-receive hook exits with a non-zero exit status no updates
+sha1-old and sha1-new should be valid objects in the repository.</p></div>
+<div class="para"><p>This hook is called before any refname is updated and before any
+fast-forward checks are performed.</p></div>
+<div class="para"><p>If the pre-receive hook exits with a non-zero exit status no updates
will be performed, and the update, post-receive and post-update
hooks will not be invoked either. This can be useful to quickly
-bail out if the update is not to be supported.</p>
+bail out if the update is not to be supported.</p></div>
</div>
-<h2>update Hook</h2>
+<h2 id="_update_hook">update Hook</h2>
<div class="sectionbody">
-<p>Before each ref is updated, if $GIT_DIR/hooks/update file exists
-and is executable, it is invoked once per ref, with three parameters:</p>
+<div class="para"><p>Before each ref is updated, if $GIT_DIR/hooks/update file exists
+and is executable, it is invoked once per ref, with three parameters:</p></div>
<div class="literalblock">
<div class="content">
<pre><tt>$GIT_DIR/hooks/update refname sha1-old sha1-new</tt></pre>
</div></div>
-<p>The refname parameter is relative to $GIT_DIR; e.g. for the master
+<div class="para"><p>The refname parameter is relative to $GIT_DIR; e.g. for the master
head this is "refs/heads/master". The two sha1 arguments are
the object names for the refname before and after the update.
Note that the hook is called before the refname is updated,
so either sha1-old is 0{40} (meaning there is no such ref yet),
-or it should match what is recorded in refname.</p>
-<p>The hook should exit with non-zero status if it wants to disallow
-updating the named ref. Otherwise it should exit with zero.</p>
-<p>Successful execution (a zero exit status) of this hook does not
+or it should match what is recorded in refname.</p></div>
+<div class="para"><p>The hook should exit with non-zero status if it wants to disallow
+updating the named ref. Otherwise it should exit with zero.</p></div>
+<div class="para"><p>Successful execution (a zero exit status) of this hook does not
ensure the ref will actually be updated, it is only a prerequisite.
As such it is not a good idea to send notices (e.g. email) from
-this hook. Consider using the post-receive hook instead.</p>
+this hook. Consider using the post-receive hook instead.</p></div>
</div>
-<h2>post-receive Hook</h2>
+<h2 id="_post_receive_hook">post-receive Hook</h2>
<div class="sectionbody">
-<p>After all refs were updated (or attempted to be updated), if any
+<div class="para"><p>After all refs were updated (or attempted to be updated), if any
ref update was successful, and if $GIT_DIR/hooks/post-receive
file exists and is executable, it will be invoke once with no
parameters. The standard input of the hook will be one line
-for each successfully updated ref:</p>
+for each successfully updated ref:</p></div>
<div class="literalblock">
<div class="content">
<pre><tt>sha1-old SP sha1-new SP refname LF</tt></pre>
</div></div>
-<p>The refname value is relative to $GIT_DIR; e.g. for the master
+<div class="para"><p>The refname value is relative to $GIT_DIR; e.g. for the master
head this is "refs/heads/master". The two sha1 values before
each refname are the object names for the refname before and after
the update. Refs that were created will have sha1-old equal to
0{40}, while refs that were deleted will have sha1-new equal to
0{40}, otherwise sha1-old and sha1-new should be valid objects in
-the repository.</p>
-<p>Using this hook, it is easy to generate mails describing the updates
+the repository.</p></div>
+<div class="para"><p>Using this hook, it is easy to generate mails describing the updates
to the repository. This example script sends one mail message per
-ref listing the commits pushed to the repository:</p>
+ref listing the commits pushed to the repository:</p></div>
<div class="literalblock">
<div class="content">
<pre><tt>#!/bin/sh
@@ -387,50 +435,50 @@ do done
exit 0</tt></pre>
</div></div>
-<p>The exit code from this hook invocation is ignored, however a
-non-zero exit code will generate an error message.</p>
-<p>Note that it is possible for refname to not have sha1-new when this
+<div class="para"><p>The exit code from this hook invocation is ignored, however a
+non-zero exit code will generate an error message.</p></div>
+<div class="para"><p>Note that it is possible for refname to not have sha1-new when this
hook runs. This can easily occur if another user modifies the ref
-after it was updated by <tt>git-receive-pack</tt>, but before the hook was able
+after it was updated by <em>git-receive-pack</em>, but before the hook was able
to evaluate it. It is recommended that hooks rely on sha1-new
-rather than the current value of refname.</p>
+rather than the current value of refname.</p></div>
</div>
-<h2>post-update Hook</h2>
+<h2 id="_post_update_hook">post-update Hook</h2>
<div class="sectionbody">
-<p>After all other processing, if at least one ref was updated, and
+<div class="para"><p>After all other processing, if at least one ref was updated, and
if $GIT_DIR/hooks/post-update file exists and is executable, then
post-update will called with the list of refs that have been updated.
-This can be used to implement any repository wide cleanup tasks.</p>
-<p>The exit code from this hook invocation is ignored; the only thing
-left for <tt>git-receive-pack</tt> to do at that point is to exit itself
-anyway.</p>
-<p>This hook can be used, for example, to run <tt>git update-server-info</tt>
-if the repository is packed and is served via a dumb transport.</p>
+This can be used to implement any repository wide cleanup tasks.</p></div>
+<div class="para"><p>The exit code from this hook invocation is ignored; the only thing
+left for <em>git-receive-pack</em> to do at that point is to exit itself
+anyway.</p></div>
+<div class="para"><p>This hook can be used, for example, to run <tt>git update-server-info</tt>
+if the repository is packed and is served via a dumb transport.</p></div>
<div class="literalblock">
<div class="content">
<pre><tt>#!/bin/sh
exec git update-server-info</tt></pre>
</div></div>
</div>
-<h2>SEE ALSO</h2>
+<h2 id="_see_also">SEE ALSO</h2>
<div class="sectionbody">
-<p><a href="git-send-pack.html">git-send-pack(1)</a></p>
+<div class="para"><p><a href="git-send-pack.html">git-send-pack(1)</a></p></div>
</div>
-<h2>Author</h2>
+<h2 id="_author">Author</h2>
<div class="sectionbody">
-<p>Written by Linus Torvalds <torvalds@osdl.org></p>
+<div class="para"><p>Written by Linus Torvalds <torvalds@osdl.org></p></div>
</div>
-<h2>Documentation</h2>
+<h2 id="_documentation">Documentation</h2>
<div class="sectionbody">
-<p>Documentation by Junio C Hamano.</p>
+<div class="para"><p>Documentation by Junio C Hamano.</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:01:58 UTC
+Last updated 2008-07-06 05:16:58 UTC
</div>
</div>
</body>
|