| blob | 574be8ebe22442fdd80f039a04cedb468f394e5d |
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 }
129 }
133 }
135 /* Block element titles. */
143 }
146 }
150 }
153 }
156 }
162 }
168 }
176 }
181 }
185 }
189 }
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
193 }
202 }
206 }
211 }
217 dl {
220 }
221 dt {
226 }
229 }
233 }
236 }
239 }
242 }
245 }
248 }
255 }
259 }
263 }
264 tfoot {
266 }
269 }
272 }
273 /* Because the table frame attribute is overriden by CSS in most browsers. */
276 }
280 }
284 }
290 }
293 }
296 }
302 }
305 }
309 }
313 }
317 }
321 }
326 }
330 }
340 }
345 }
347 div#toc {
349 }
351 div#toctitle {
358 }
363 }
367 }
371 }
375 }
376 /* Overrides for manpage documents */
377 h1 {
382 }
383 h2 {
385 }
388 }
392 }
394 /* Workarounds for IE6's broken and incomplete CSS2. */
400 }
407 }
413 }
418 }
422 }
426 }
431 }
433 /* IE6 sets dynamically generated links as visited. */
435 </style>
437 /*<![CDATA[*/
441 /////////////////////////////////////////////////////////////////////
442 // Table Of Contents generator
443 /////////////////////////////////////////////////////////////////////
445 /* Author: Mihai Bazon, September 2002
446 * http://students.infoiasi.ro/~mishoo
447 *
448 * Table Of Content generator
449 * Version: 0.4
450 *
451 * Feel free to use this script under the terms of the GNU General Public
452 * License, as long as you do not remove or alter this notice.
453 */
455 /* modified by Troy D. Hanson, September 2006. License: GPL */
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
458 // toclevels = 1..4.
468 }
470 }
476 }
481 // Function that scans the DOM tree for header elements (the DOM2
482 // nodeIterator API would be a better technique but not supported by all
483 // browsers).
490 }
492 }
493 }
494 }
497 }
512 }
515 },
518 /////////////////////////////////////////////////////////////////////
519 // Footnotes generator
520 /////////////////////////////////////////////////////////////////////
522 /* Based on footnote generation code from:
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
524 */
534 n++;
535 // Use [\s\S] in place of . so multi-line matches work.
536 // Because JavaScript has no s (dotall) regex flag.
547 }
548 }
552 // Process footnoterefs.
561 }
562 }
563 }
564 }
566 }
567 /*]]>*/
568 </script>
569 </head>
570 <body>
572 <h1>
573 git-receive-pack(1) Manual Page
574 </h1>
577 <p>git-receive-pack -
578 Receive what is pushed into the repository
579 </p>
580 </div>
581 </div>
588 </div></div>
589 </div>
593 information fed from the remote end.</p></div>
596 program pair is meant to be used to push updates to remote
597 repository. For pull operations, see <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.</p></div>
599 (heads/tags) on the remote end (strictly speaking, it is the
601 the send-pack end, it is updating the remote. Confused?)</p></div>
603 post-update hooks found in the Documentation/howto directory.</p></div>
604 <div class="paragraph"><p><em>git-receive-pack</em> honours the receive.denyNonFastForwards config
605 option, which tells it if updates to a ref should be denied if they
606 are not fast-forwards.</p></div>
607 </div>
613 </dt>
614 <dd>
615 <p>
616 The repository to sync into.
617 </p>
618 </dd>
619 </dl></div>
620 </div>
624 and is executable, it will be invoked once with no parameters. The
625 standard input of the hook will be one line per ref to be updated:</p></div>
629 </div></div>
631 head this is "refs/heads/master". The two sha1 values before
632 each refname are the object names for the refname before and after
635 sha1-old and sha1-new should be valid objects in the repository.</p></div>
637 fast-forward checks are performed.</p></div>
639 will be performed, and the update, post-receive and post-update
640 hooks will not be invoked either. This can be useful to quickly
641 bail out if the update is not to be supported.</p></div>
642 </div>
646 and is executable, it is invoked once per ref, with three parameters:</p></div>
650 </div></div>
652 head this is "refs/heads/master". The two sha1 arguments are
653 the object names for the refname before and after the update.
654 Note that the hook is called before the refname is updated,
656 or it should match what is recorded in refname.</p></div>
658 updating the named ref. Otherwise it should exit with zero.</p></div>
660 ensure the ref will actually be updated, it is only a prerequisite.
661 As such it is not a good idea to send notices (e.g. email) from
662 this hook. Consider using the post-receive hook instead.</p></div>
663 </div>
667 ref update was successful, and if $GIT_DIR/hooks/post-receive
668 file exists and is executable, it will be invoked once with no
669 parameters. The standard input of the hook will be one line
670 for each successfully updated ref:</p></div>
674 </div></div>
676 head this is "refs/heads/master". The two sha1 values before
677 each refname are the object names for the refname before and after
678 the update. Refs that were created will have sha1-old equal to
681 the repository.</p></div>
683 to the repository. This example script sends one mail message per
684 ref listing the commits pushed to the repository:</p></div>
687 <pre><tt>#!/bin/sh
688 # mail out commit update information.
689 while read oval nval ref
690 do
692 then
693 echo "Created a new ref, with the following commits:"
694 git rev-list --pretty "$nval"
695 else
696 echo "New commits:"
698 fi |
699 mail -s "Changes to ref $ref" commit-list@mydomain
700 done
702 </div></div>
704 non-zero exit code will generate an error message.</p></div>
706 hook runs. This can easily occur if another user modifies the ref
708 to evaluate it. It is recommended that hooks rely on sha1-new
709 rather than the current value of refname.</p></div>
710 </div>
714 if $GIT_DIR/hooks/post-update file exists and is executable, then
715 post-update will be called with the list of refs that have been updated.
716 This can be used to implement any repository wide cleanup tasks.</p></div>
719 anyway.</p></div>
720 <div class="paragraph"><p>This hook can be used, for example, to run <tt>git update-server-info</tt>
721 if the repository is packed and is served via a dumb transport.</p></div>
724 <pre><tt>#!/bin/sh
725 exec git update-server-info</tt></pre>
726 </div></div>
727 </div>
730 <div class="paragraph"><p><a href="git-send-pack.html">git-send-pack(1)</a>, <a href="gitnamespaces.html">gitnamespaces(7)</a></p></div>
731 </div>
735 </div>
736 </div>
741 </div>
742 </div>
743 </body>
744 </html>