| blob | 406d0da09eab127d49f3754218e796bbced62b4d |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-receive-pack(1) Manual Page
313 </h1>
316 <p>git-receive-pack -
317 Receive what is pushed into the repository
318 </p>
319 </div>
320 </div>
324 </div>
328 information fed from the remote end.</p></div>
331 program pair is meant to be used to push updates to remote
332 repository. For pull operations, see <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.</p></div>
334 (heads/tags) on the remote end (strictly speaking, it is the
336 the send-pack end, it is updating the remote. Confused?)</p></div>
338 post-update hooks found in the Documentation/howto directory.</p></div>
340 option, which tells it if updates to a ref should be denied if they
341 are not fast-forwards.</p></div>
342 </div>
346 <dt>
348 </dt>
349 <dd>
350 <p>
351 The repository to sync into.
352 </p>
353 </dd>
354 </dl></div>
355 </div>
359 and is executable, it will be invoked once with no parameters. The
360 standard input of the hook will be one line per ref to be updated:</p></div>
364 </div></div>
366 head this is "refs/heads/master". The two sha1 values before
367 each refname are the object names for the refname before and after
370 sha1-old and sha1-new should be valid objects in the repository.</p></div>
372 fast-forward checks are performed.</p></div>
374 will be performed, and the update, post-receive and post-update
375 hooks will not be invoked either. This can be useful to quickly
376 bail out if the update is not to be supported.</p></div>
377 </div>
381 and is executable, it is invoked once per ref, with three parameters:</p></div>
385 </div></div>
387 head this is "refs/heads/master". The two sha1 arguments are
388 the object names for the refname before and after the update.
389 Note that the hook is called before the refname is updated,
391 or it should match what is recorded in refname.</p></div>
393 updating the named ref. Otherwise it should exit with zero.</p></div>
395 ensure the ref will actually be updated, it is only a prerequisite.
396 As such it is not a good idea to send notices (e.g. email) from
397 this hook. Consider using the post-receive hook instead.</p></div>
398 </div>
402 ref update was successful, and if $GIT_DIR/hooks/post-receive
403 file exists and is executable, it will be invoked once with no
404 parameters. The standard input of the hook will be one line
405 for each successfully updated ref:</p></div>
409 </div></div>
411 head this is "refs/heads/master". The two sha1 values before
412 each refname are the object names for the refname before and after
413 the update. Refs that were created will have sha1-old equal to
416 the repository.</p></div>
418 to the repository. This example script sends one mail message per
419 ref listing the commits pushed to the repository:</p></div>
422 <pre><tt>#!/bin/sh
423 # mail out commit update information.
424 while read oval nval ref
425 do
427 then
428 echo "Created a new ref, with the following commits:"
429 git rev-list --pretty "$nval"
430 else
431 echo "New commits:"
433 fi |
434 mail -s "Changes to ref $ref" commit-list@mydomain
435 done
437 </div></div>
439 non-zero exit code will generate an error message.</p></div>
441 hook runs. This can easily occur if another user modifies the ref
443 to evaluate it. It is recommended that hooks rely on sha1-new
444 rather than the current value of refname.</p></div>
445 </div>
449 if $GIT_DIR/hooks/post-update file exists and is executable, then
450 post-update will be called with the list of refs that have been updated.
451 This can be used to implement any repository wide cleanup tasks.</p></div>
454 anyway.</p></div>
456 if the repository is packed and is served via a dumb transport.</p></div>
459 <pre><tt>#!/bin/sh
460 exec git update-server-info</tt></pre>
461 </div></div>
462 </div>
466 </div>
470 </div>
474 </div>
478 </div>
482 </div>
483 </div>
484 </body>
485 </html>