| blob | 2f143db074f63f2ed517a3d7c7e43186dd132050 |
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>
418 </div>
422 information fed from the remote end.</p></div>
425 program pair is meant to be used to push updates to remote
426 repository. For pull operations, see <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.</p></div>
428 (heads/tags) on the remote end (strictly speaking, it is the
430 the send-pack end, it is updating the remote. Confused?)</p></div>
432 post-update hooks found in the Documentation/howto directory.</p></div>
433 <div class="paragraph"><p><em>git-receive-pack</em> honours the receive.denyNonFastForwards config
434 option, which tells it if updates to a ref should be denied if they
435 are not fast-forwards.</p></div>
436 </div>
442 </dt>
443 <dd>
444 <p>
445 The repository to sync into.
446 </p>
447 </dd>
448 </dl></div>
449 </div>
453 and is executable, it will be invoked once with no parameters. The
454 standard input of the hook will be one line per ref to be updated:</p></div>
458 </div></div>
460 head this is "refs/heads/master". The two sha1 values before
461 each refname are the object names for the refname before and after
464 sha1-old and sha1-new should be valid objects in the repository.</p></div>
466 fast-forward checks are performed.</p></div>
468 will be performed, and the update, post-receive and post-update
469 hooks will not be invoked either. This can be useful to quickly
470 bail out if the update is not to be supported.</p></div>
471 </div>
475 and is executable, it is invoked once per ref, with three parameters:</p></div>
479 </div></div>
481 head this is "refs/heads/master". The two sha1 arguments are
482 the object names for the refname before and after the update.
483 Note that the hook is called before the refname is updated,
485 or it should match what is recorded in refname.</p></div>
487 updating the named ref. Otherwise it should exit with zero.</p></div>
489 ensure the ref will actually be updated, it is only a prerequisite.
490 As such it is not a good idea to send notices (e.g. email) from
491 this hook. Consider using the post-receive hook instead.</p></div>
492 </div>
496 ref update was successful, and if $GIT_DIR/hooks/post-receive
497 file exists and is executable, it will be invoked once with no
498 parameters. The standard input of the hook will be one line
499 for each successfully updated ref:</p></div>
503 </div></div>
505 head this is "refs/heads/master". The two sha1 values before
506 each refname are the object names for the refname before and after
507 the update. Refs that were created will have sha1-old equal to
510 the repository.</p></div>
512 to the repository. This example script sends one mail message per
513 ref listing the commits pushed to the repository:</p></div>
516 <pre><tt>#!/bin/sh
517 # mail out commit update information.
518 while read oval nval ref
519 do
521 then
522 echo "Created a new ref, with the following commits:"
523 git rev-list --pretty "$nval"
524 else
525 echo "New commits:"
527 fi |
528 mail -s "Changes to ref $ref" commit-list@mydomain
529 done
531 </div></div>
533 non-zero exit code will generate an error message.</p></div>
535 hook runs. This can easily occur if another user modifies the ref
537 to evaluate it. It is recommended that hooks rely on sha1-new
538 rather than the current value of refname.</p></div>
539 </div>
543 if $GIT_DIR/hooks/post-update file exists and is executable, then
544 post-update will be called with the list of refs that have been updated.
545 This can be used to implement any repository wide cleanup tasks.</p></div>
548 anyway.</p></div>
549 <div class="paragraph"><p>This hook can be used, for example, to run <tt>git update-server-info</tt>
550 if the repository is packed and is served via a dumb transport.</p></div>
553 <pre><tt>#!/bin/sh
554 exec git update-server-info</tt></pre>
555 </div></div>
556 </div>
560 </div>
564 </div>
568 </div>
569 </div>
570 </body>
571 </html>