| blob | 0bc951857a75c3414d30a5f23aa61bc9b7a1b737 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-receive-pack(1) Manual Page
407 </h1>
410 <p>git-receive-pack -
411 Receive what is pushed into the repository
412 </p>
413 </div>
414 </div>
420 </div></div>
421 </div>
425 information fed from the remote end.</p></div>
428 program pair is meant to be used to push updates to remote
429 repository. For pull operations, see <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.</p></div>
431 (heads/tags) on the remote end (strictly speaking, it is the
433 the send-pack end, it is updating the remote. Confused?)</p></div>
435 post-update hooks found in the Documentation/howto directory.</p></div>
436 <div class="paragraph"><p><em>git-receive-pack</em> honours the receive.denyNonFastForwards config
437 option, which tells it if updates to a ref should be denied if they
438 are not fast-forwards.</p></div>
439 </div>
445 </dt>
446 <dd>
447 <p>
448 The repository to sync into.
449 </p>
450 </dd>
451 </dl></div>
452 </div>
456 and is executable, it will be invoked once with no parameters. The
457 standard input of the hook will be one line per ref to be updated:</p></div>
461 </div></div>
463 head this is "refs/heads/master". The two sha1 values before
464 each refname are the object names for the refname before and after
467 sha1-old and sha1-new should be valid objects in the repository.</p></div>
469 fast-forward checks are performed.</p></div>
471 will be performed, and the update, post-receive and post-update
472 hooks will not be invoked either. This can be useful to quickly
473 bail out if the update is not to be supported.</p></div>
474 </div>
478 and is executable, it is invoked once per ref, with three parameters:</p></div>
482 </div></div>
484 head this is "refs/heads/master". The two sha1 arguments are
485 the object names for the refname before and after the update.
486 Note that the hook is called before the refname is updated,
488 or it should match what is recorded in refname.</p></div>
490 updating the named ref. Otherwise it should exit with zero.</p></div>
492 ensure the ref will actually be updated, it is only a prerequisite.
493 As such it is not a good idea to send notices (e.g. email) from
494 this hook. Consider using the post-receive hook instead.</p></div>
495 </div>
499 ref update was successful, and if $GIT_DIR/hooks/post-receive
500 file exists and is executable, it will be invoked once with no
501 parameters. The standard input of the hook will be one line
502 for each successfully updated ref:</p></div>
506 </div></div>
508 head this is "refs/heads/master". The two sha1 values before
509 each refname are the object names for the refname before and after
510 the update. Refs that were created will have sha1-old equal to
513 the repository.</p></div>
515 to the repository. This example script sends one mail message per
516 ref listing the commits pushed to the repository:</p></div>
519 <pre><tt>#!/bin/sh
520 # mail out commit update information.
521 while read oval nval ref
522 do
524 then
525 echo "Created a new ref, with the following commits:"
526 git rev-list --pretty "$nval"
527 else
528 echo "New commits:"
530 fi |
531 mail -s "Changes to ref $ref" commit-list@mydomain
532 done
534 </div></div>
536 non-zero exit code will generate an error message.</p></div>
538 hook runs. This can easily occur if another user modifies the ref
540 to evaluate it. It is recommended that hooks rely on sha1-new
541 rather than the current value of refname.</p></div>
542 </div>
546 if $GIT_DIR/hooks/post-update file exists and is executable, then
547 post-update will be called with the list of refs that have been updated.
548 This can be used to implement any repository wide cleanup tasks.</p></div>
551 anyway.</p></div>
552 <div class="paragraph"><p>This hook can be used, for example, to run <tt>git update-server-info</tt>
553 if the repository is packed and is served via a dumb transport.</p></div>
556 <pre><tt>#!/bin/sh
557 exec git update-server-info</tt></pre>
558 </div></div>
559 </div>
563 </div>
567 </div>
571 </div>
572 </div>
573 </body>
574 </html>