blob: 6836f8bc2223d25906c764348a1308d69334ea48 [file] [log] [blame]
Junio C Hamano1a4e8412005-12-27 08:17:231<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
Junio C Hamanoba4b9282008-07-06 05:20:316<meta name="generator" content="AsciiDoc 8.2.5" />
Junio C Hamano1a4e8412005-12-27 08:17:237<style type="text/css">
8/* Debug borders */
9p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
10/*
11 border: 1px solid red;
12*/
13}
14
15body {
16 margin: 1em 5% 1em 5%;
17}
18
Junio C Hamanoba4b9282008-07-06 05:20:3119a {
20 color: blue;
21 text-decoration: underline;
22}
23a:visited {
24 color: fuchsia;
25}
Junio C Hamano1a4e8412005-12-27 08:17:2326
27em {
28 font-style: italic;
29}
30
31strong {
32 font-weight: bold;
33}
34
35tt {
36 color: navy;
37}
38
39h1, h2, h3, h4, h5, h6 {
40 color: #527bbd;
41 font-family: sans-serif;
42 margin-top: 1.2em;
43 margin-bottom: 0.5em;
44 line-height: 1.3;
45}
46
Junio C Hamanoba4b9282008-07-06 05:20:3147h1, h2, h3 {
Junio C Hamano1a4e8412005-12-27 08:17:2348 border-bottom: 2px solid silver;
49}
50h2 {
Junio C Hamano1a4e8412005-12-27 08:17:2351 padding-top: 0.5em;
52}
Junio C Hamanoba4b9282008-07-06 05:20:3153h3 {
54 float: left;
55}
56h3 + * {
57 clear: left;
58}
Junio C Hamano1a4e8412005-12-27 08:17:2359
60div.sectionbody {
61 font-family: serif;
62 margin-left: 0;
63}
64
65hr {
66 border: 1px solid silver;
67}
68
69p {
70 margin-top: 0.5em;
71 margin-bottom: 0.5em;
72}
73
74pre {
75 padding: 0;
76 margin: 0;
77}
78
79span#author {
80 color: #527bbd;
81 font-family: sans-serif;
82 font-weight: bold;
Junio C Hamanoba4b9282008-07-06 05:20:3183 font-size: 1.1em;
Junio C Hamano1a4e8412005-12-27 08:17:2384}
85span#email {
86}
87span#revision {
88 font-family: sans-serif;
89}
90
91div#footer {
92 font-family: sans-serif;
93 font-size: small;
94 border-top: 2px solid silver;
95 padding-top: 0.5em;
96 margin-top: 4.0em;
97}
98div#footer-text {
99 float: left;
100 padding-bottom: 0.5em;
101}
102div#footer-badges {
103 float: right;
104 padding-bottom: 0.5em;
105}
106
107div#preamble,
108div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
109div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
110div.admonitionblock {
111 margin-right: 10%;
112 margin-top: 1.5em;
113 margin-bottom: 1.5em;
114}
115div.admonitionblock {
116 margin-top: 2.5em;
117 margin-bottom: 2.5em;
118}
119
120div.content { /* Block element content. */
121 padding: 0;
122}
123
124/* Block element titles. */
125div.title, caption.title {
126 font-family: sans-serif;
127 font-weight: bold;
128 text-align: left;
129 margin-top: 1.0em;
130 margin-bottom: 0.5em;
131}
132div.title + * {
133 margin-top: 0;
134}
135
136td div.title:first-child {
137 margin-top: 0.0em;
138}
139div.content div.title:first-child {
140 margin-top: 0.0em;
141}
142div.content + div.title {
143 margin-top: 0.0em;
144}
145
146div.sidebarblock > div.content {
147 background: #ffffee;
148 border: 1px solid silver;
149 padding: 0.5em;
150}
151
Junio C Hamanoba4b9282008-07-06 05:20:31152div.listingblock {
153 margin-right: 0%;
154}
Junio C Hamano1a4e8412005-12-27 08:17:23155div.listingblock > div.content {
156 border: 1px solid silver;
157 background: #f4f4f4;
158 padding: 0.5em;
159}
160
161div.quoteblock > div.content {
162 padding-left: 2.0em;
163}
Junio C Hamanoba4b9282008-07-06 05:20:31164
165div.attribution {
Junio C Hamano1a4e8412005-12-27 08:17:23166 text-align: right;
167}
Junio C Hamanoba4b9282008-07-06 05:20:31168div.verseblock + div.attribution {
169 text-align: left;
170}
Junio C Hamano1a4e8412005-12-27 08:17:23171
172div.admonitionblock .icon {
173 vertical-align: top;
174 font-size: 1.1em;
175 font-weight: bold;
176 text-decoration: underline;
177 color: #527bbd;
178 padding-right: 0.5em;
179}
180div.admonitionblock td.content {
181 padding-left: 0.5em;
182 border-left: 2px solid silver;
183}
184
185div.exampleblock > div.content {
186 border-left: 2px solid silver;
187 padding: 0.5em;
188}
189
190div.verseblock div.content {
191 white-space: pre;
192}
193
194div.imageblock div.content { padding-left: 0; }
195div.imageblock img { border: 1px solid silver; }
196span.image img { border-style: none; }
197
198dl {
199 margin-top: 0.8em;
200 margin-bottom: 0.8em;
201}
202dt {
203 margin-top: 0.5em;
204 margin-bottom: 0;
205 font-style: italic;
206}
207dd > *:first-child {
208 margin-top: 0;
209}
210
211ul, ol {
212 list-style-position: outside;
213}
Junio C Hamanoba4b9282008-07-06 05:20:31214div.olist2 ol {
Junio C Hamano1a4e8412005-12-27 08:17:23215 list-style-type: lower-alpha;
216}
217
218div.tableblock > table {
Junio C Hamanoba4b9282008-07-06 05:20:31219 border: 3px solid #527bbd;
Junio C Hamano1a4e8412005-12-27 08:17:23220}
221thead {
222 font-family: sans-serif;
223 font-weight: bold;
224}
225tfoot {
226 font-weight: bold;
227}
228
229div.hlist {
230 margin-top: 0.8em;
231 margin-bottom: 0.8em;
232}
Junio C Hamanoba4b9282008-07-06 05:20:31233div.hlist td {
234 padding-bottom: 5px;
235}
Junio C Hamano1a4e8412005-12-27 08:17:23236td.hlist1 {
237 vertical-align: top;
238 font-style: italic;
239 padding-right: 0.8em;
240}
241td.hlist2 {
242 vertical-align: top;
243}
244
245@media print {
246 div#footer-badges { display: none; }
247}
Junio C Hamanoba4b9282008-07-06 05:20:31248
249div#toctitle {
250 color: #527bbd;
251 font-family: sans-serif;
252 font-size: 1.1em;
253 font-weight: bold;
254 margin-top: 1.0em;
255 margin-bottom: 0.1em;
256}
257
258div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
259 margin-top: 0;
260 margin-bottom: 0;
261}
262div.toclevel2 {
263 margin-left: 2em;
264 font-size: 0.9em;
265}
266div.toclevel3 {
267 margin-left: 4em;
268 font-size: 0.9em;
269}
270div.toclevel4 {
271 margin-left: 6em;
272 font-size: 0.9em;
273}
274include1::./stylesheets/xhtml11-manpage.css[]
Junio C Hamano1a4e8412005-12-27 08:17:23275/* Workarounds for IE6's broken and incomplete CSS2. */
276
277div.sidebar-content {
278 background: #ffffee;
279 border: 1px solid silver;
280 padding: 0.5em;
281}
282div.sidebar-title, div.image-title {
283 font-family: sans-serif;
284 font-weight: bold;
285 margin-top: 0.0em;
286 margin-bottom: 0.5em;
287}
288
289div.listingblock div.content {
290 border: 1px solid silver;
291 background: #f4f4f4;
292 padding: 0.5em;
293}
294
295div.quoteblock-content {
296 padding-left: 2.0em;
297}
298
299div.exampleblock-content {
300 border-left: 2px solid silver;
301 padding-left: 0.5em;
302}
Junio C Hamanoba4b9282008-07-06 05:20:31303
304/* IE6 sets dynamically generated links as visited. */
305div#toc a:visited { color: blue; }
Junio C Hamano1a4e8412005-12-27 08:17:23306</style>
307<title>git-push(1)</title>
308</head>
309<body>
310<div id="header">
311<h1>
312git-push(1) Manual Page
313</h1>
314<h2>NAME</h2>
315<div class="sectionbody">
316<p>git-push -
Junio C Hamano01078922006-03-10 00:31:47317 Update remote refs along with associated objects
Junio C Hamano1a4e8412005-12-27 08:17:23318</p>
319</div>
320</div>
321<h2>SYNOPSIS</h2>
322<div class="sectionbody">
Junio C Hamanoa9b8d242007-05-19 04:51:55323<div class="verseblock">
Junio C Hamanoa476efa2008-10-10 15:31:42324<div class="content"><em>git push</em> [--all | --mirror] [--dry-run] [--tags] [--receive-pack=&lt;git-receive-pack&gt;]
325 [--repo=&lt;repository&gt;] [-f | --force] [-v | --verbose]
Junio C Hamano7f80ae82008-07-30 18:31:35326 [&lt;repository&gt; &lt;refspec&gt;&#8230;]</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23327</div>
Junio C Hamanoba4b9282008-07-06 05:20:31328<h2 id="_description">DESCRIPTION</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23329<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31330<div class="para"><p>Updates remote refs using local refs, while sending objects
331necessary to complete the given refs.</p></div>
332<div class="para"><p>You can make interesting things happen to a repository
Junio C Hamano1a4e8412005-12-27 08:17:23333every time you push into it, by setting up <em>hooks</em> there. See
Junio C Hamanoba4b9282008-07-06 05:20:31334documentation for <a href="git-receive-pack.html">git-receive-pack(1)</a>.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23335</div>
Junio C Hamanoba4b9282008-07-06 05:20:31336<h2 id="_options">OPTIONS</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23337<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31338<div class="vlist"><dl>
Junio C Hamano1a4e8412005-12-27 08:17:23339<dt>
340&lt;repository&gt;
341</dt>
342<dd>
343<p>
Junio C Hamano40f2f8d2006-02-07 08:04:39344 The "remote" repository that is destination of a push
345 operation. See the section <a href="#URLS">GIT URLS</a> below.
Junio C Hamano1a4e8412005-12-27 08:17:23346</p>
Junio C Hamano40f2f8d2006-02-07 08:04:39347</dd>
348<dt>
Junio C Hamano7f80ae82008-07-30 18:31:35349&lt;refspec&gt;&#8230;
Junio C Hamano40f2f8d2006-02-07 08:04:39350</dt>
351<dd>
352<p>
Junio C Hamanofaa1e502008-08-10 03:55:58353 The canonical format of a &lt;refspec&gt; parameter is
354 <tt>+?&lt;src&gt;:&lt;dst&gt;</tt>; that is, an optional plus <tt>&#43;</tt>, followed
Junio C Hamano40f2f8d2006-02-07 08:04:39355 by the source ref, followed by a colon <tt>:</tt>, followed by
356 the destination ref.
357</p>
Junio C Hamanoba4b9282008-07-06 05:20:31358<div class="para"><p>The &lt;src&gt; side represents the source branch (or arbitrary
Junio C Hamanoa9aee782008-04-23 16:09:20359"SHA1 expression", such as <tt>master~4</tt> (four parents before the
360tip of <tt>master</tt> branch); see <a href="git-rev-parse.html">git-rev-parse(1)</a>) that you
Junio C Hamanoba4b9282008-07-06 05:20:31361want to push. The &lt;dst&gt; side represents the destination location.</p></div>
362<div class="para"><p>The local ref that matches &lt;src&gt; is used
Junio C Hamanoa9aee782008-04-23 16:09:20363to fast forward the remote ref that matches &lt;dst&gt; (or, if no &lt;dst&gt; was
364specified, the same ref that &lt;src&gt; referred to locally). If
365the optional leading plus <tt>+</tt> is used, the remote ref is updated
Junio C Hamanoba4b9282008-07-06 05:20:31366even if it does not result in a fast forward update.</p></div>
367<div class="para"><p><tt>tag &lt;tag&gt;</tt> means the same as <tt>refs/tags/&lt;tag&gt;:refs/tags/&lt;tag&gt;</tt>.</p></div>
368<div class="para"><p>A parameter &lt;ref&gt; without a colon pushes the &lt;ref&gt; from the source
369repository to the destination repository under the same name.</p></div>
370<div class="para"><p>Pushing an empty &lt;src&gt; allows you to delete the &lt;dst&gt; ref from
371the remote repository.</p></div>
372<div class="para"><p>The special refspec <tt>:</tt> (or <tt>+:</tt> to allow non-fast forward updates)
Junio C Hamanob713ff12008-05-24 01:12:30373directs git to push "matching" heads: for every head that exists on
374the local side, the remote side is updated if a head of the same name
375already exists on the remote side. This is the default operation mode
376if no explicit refspec is found (that is neither on the command line
Junio C Hamanoba4b9282008-07-06 05:20:31377nor in any Push line of the corresponding remotes file---see below).</p></div>
Junio C Hamano40f2f8d2006-02-07 08:04:39378</dd>
379<dt>
380--all
381</dt>
382<dd>
383<p>
384 Instead of naming each ref to push, specifies that all
Junio C Hamanod2d9ae12007-09-19 02:27:57385 refs under <tt>$GIT_DIR/refs/heads/</tt> be pushed.
Junio C Hamano40f2f8d2006-02-07 08:04:39386</p>
387</dd>
388<dt>
Junio C Hamano9d2bbb72007-11-25 04:56:07389--mirror
390</dt>
391<dd>
392<p>
393 Instead of naming each ref to push, specifies that all
Junio C Hamanoa351d142008-06-21 09:40:40394 refs under <tt>$GIT_DIR/refs/</tt> (which includes but is not
395 limited to <tt>refs/heads/</tt>, <tt>refs/remotes/</tt>, and <tt>refs/tags/</tt>)
Junio C Hamano9d2bbb72007-11-25 04:56:07396 be mirrored to the remote repository. Newly created local
397 refs will be pushed to the remote end, locally updated refs
398 will be force updated on the remote end, and deleted refs
Junio C Hamano47d68a52008-05-06 06:35:40399 will be removed from the remote end. This is the default
400 if the configuration option <tt>remote.&lt;remote&gt;.mirror</tt> is
401 set.
Junio C Hamano9d2bbb72007-11-25 04:56:07402</p>
403</dd>
404<dt>
Junio C Hamano764a6672007-10-23 01:23:31405--dry-run
406</dt>
407<dd>
408<p>
409 Do everything except actually send the updates.
410</p>
411</dd>
412<dt>
Junio C Hamano40f2f8d2006-02-07 08:04:39413--tags
414</dt>
415<dd>
416<p>
417 All refs under <tt>$GIT_DIR/refs/tags</tt> are pushed, in
418 addition to refspecs explicitly listed on the command
419 line.
420</p>
421</dd>
422<dt>
Junio C Hamano4ad294b2007-01-20 02:22:50423--receive-pack=&lt;git-receive-pack&gt;
Junio C Hamano1ce39ab2007-01-16 22:05:10424</dt>
425<dd>
426<p>
Junio C Hamanoba4b9282008-07-06 05:20:31427 Path to the <em>git-receive-pack</em> program on the remote
Junio C Hamano1ce39ab2007-01-16 22:05:10428 end. Sometimes useful when pushing to a remote
429 repository over ssh, and you do not have the program in
430 a directory on the default $PATH.
431</p>
432</dd>
433<dt>
Junio C Hamano4ad294b2007-01-20 02:22:50434--exec=&lt;git-receive-pack&gt;
435</dt>
436<dd>
437<p>
438 Same as --receive-pack=&lt;git-receive-pack&gt;.
439</p>
440</dd>
441<dt>
Junio C Hamanoeb415992008-06-08 22:49:47442-f
443</dt>
444<dt>
445--force
Junio C Hamano40f2f8d2006-02-07 08:04:39446</dt>
447<dd>
448<p>
449 Usually, the command refuses to update a remote ref that is
Junio C Hamano4cd1c0e2007-08-06 04:39:14450 not an ancestor of the local ref used to overwrite it.
Junio C Hamano40f2f8d2006-02-07 08:04:39451 This flag disables the check. This can cause the
452 remote repository to lose commits; use it with care.
453</p>
454</dd>
Junio C Hamano1ce39ab2007-01-16 22:05:10455<dt>
Junio C Hamanoa476efa2008-10-10 15:31:42456--repo=&lt;repository&gt;
Junio C Hamano1ce39ab2007-01-16 22:05:10457</dt>
458<dd>
459<p>
Junio C Hamanoa476efa2008-10-10 15:31:42460 This option is only relevant if no &lt;repository&gt; argument is
461 passed in the invocation. In this case, <em>git-push</em> derives the
462 remote name from the current branch: If it tracks a remote
463 branch, then that remote repository is pushed to. Otherwise,
464 the name "origin" is used. For this latter case, this option
465 can be used to override the name "origin". In other words,
466 the difference between these two commands
Junio C Hamano1ce39ab2007-01-16 22:05:10467</p>
Junio C Hamanoa476efa2008-10-10 15:31:42468<div class="listingblock">
469<div class="content">
470<pre><tt>git push public #1
471git push --repo=public #2</tt></pre>
472</div></div>
473<div class="para"><p>is that #1 always pushes to "public" whereas #2 pushes to "public"
474only if the current branch does not track a remote branch. This is
475useful if you write an alias or script around <em>git-push</em>.</p></div>
Junio C Hamano1ce39ab2007-01-16 22:05:10476</dd>
477<dt>
Junio C Hamanoeb415992008-06-08 22:49:47478--thin
479</dt>
480<dt>
481--no-thin
Junio C Hamano1ce39ab2007-01-16 22:05:10482</dt>
483<dd>
484<p>
Junio C Hamanoba4b9282008-07-06 05:20:31485 These options are passed to <em>git-send-pack</em>. Thin
Junio C Hamano1ce39ab2007-01-16 22:05:10486 transfer spends extra cycles to minimize the number of
487 objects to be sent and meant to be used on slower connection.
488</p>
489</dd>
490<dt>
Junio C Hamanoeb415992008-06-08 22:49:47491-v
492</dt>
493<dt>
494--verbose
Junio C Hamano1ce39ab2007-01-16 22:05:10495</dt>
496<dd>
497<p>
498 Run verbosely.
499</p>
500</dd>
Junio C Hamanoba4b9282008-07-06 05:20:31501</dl></div>
Junio C Hamano40f2f8d2006-02-07 08:04:39502</div>
Junio C Hamanoba4b9282008-07-06 05:20:31503<h2 id="_git_urls_a_id_urls_a">GIT URLS<a id="URLS"></a></h2>
Junio C Hamano40f2f8d2006-02-07 08:04:39504<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31505<div class="para"><p>One of the following notations can be used
506to name the remote repository:</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23507<div class="exampleblock">
508<div class="exampleblock-content">
Junio C Hamanoba4b9282008-07-06 05:20:31509<div class="ilist"><ul>
Junio C Hamano1a4e8412005-12-27 08:17:23510<li>
511<p>
512rsync://host.xz/path/to/repo.git/
513</p>
514</li>
515<li>
516<p>
517http://host.xz/path/to/repo.git/
518</p>
519</li>
520<li>
521<p>
522https://host.xz/path/to/repo.git/
523</p>
524</li>
525<li>
526<p>
527git://host.xz/path/to/repo.git/
528</p>
529</li>
530<li>
531<p>
532git://host.xz/~user/path/to/repo.git/
533</p>
534</li>
535<li>
536<p>
Junio C Hamanodbb64592007-09-01 11:17:39537ssh://&#91;user@&#93;host.xz&#91;:port&#93;/path/to/repo.git/
538</p>
539</li>
540<li>
541<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40542ssh://&#91;user@&#93;host.xz/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23543</p>
544</li>
545<li>
546<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40547ssh://&#91;user@&#93;host.xz/~user/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23548</p>
549</li>
550<li>
551<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40552ssh://&#91;user@&#93;host.xz/~/path/to/repo.git
Junio C Hamano1a4e8412005-12-27 08:17:23553</p>
554</li>
Junio C Hamanoba4b9282008-07-06 05:20:31555</ul></div>
Junio C Hamano1a4e8412005-12-27 08:17:23556</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31557<div class="para"><p>SSH is the default transport protocol over the network. You can
Junio C Hamanob1d6e882007-08-11 08:30:16558optionally specify which user to log-in as, and an alternate,
559scp-like syntax is also supported. Both syntaxes support
Junio C Hamanodbb64592007-09-01 11:17:39560username expansion, as does the native git protocol, but
561only the former supports port specification. The following
Junio C Hamanoba4b9282008-07-06 05:20:31562three are identical to the last three above, respectively:</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23563<div class="exampleblock">
564<div class="exampleblock-content">
Junio C Hamanoba4b9282008-07-06 05:20:31565<div class="ilist"><ul>
Junio C Hamano1a4e8412005-12-27 08:17:23566<li>
567<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40568&#91;user@&#93;host.xz:/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23569</p>
570</li>
571<li>
572<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40573&#91;user@&#93;host.xz:~user/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23574</p>
575</li>
576<li>
577<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40578&#91;user@&#93;host.xz:path/to/repo.git
Junio C Hamano1a4e8412005-12-27 08:17:23579</p>
580</li>
Junio C Hamanoba4b9282008-07-06 05:20:31581</ul></div>
Junio C Hamano1a4e8412005-12-27 08:17:23582</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31583<div class="para"><p>To sync with a local directory, you can use:</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23584<div class="exampleblock">
585<div class="exampleblock-content">
Junio C Hamanoba4b9282008-07-06 05:20:31586<div class="ilist"><ul>
Junio C Hamano1a4e8412005-12-27 08:17:23587<li>
588<p>
589/path/to/repo.git/
590</p>
591</li>
Junio C Hamanob1d6e882007-08-11 08:30:16592<li>
593<p>
594file:///path/to/repo.git/
595</p>
596</li>
Junio C Hamanoba4b9282008-07-06 05:20:31597</ul></div>
Junio C Hamano1a4e8412005-12-27 08:17:23598</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31599<div class="para"><p>They are mostly equivalent, except when cloning. See
600<a href="git-clone.html">git-clone(1)</a> for details.</p></div>
601<div class="para"><p>If there are a large number of similarly-named remote repositories and
Junio C Hamano24bc09a2008-02-28 00:27:44602you want to use a different format for them (such that the URLs you
603use will be rewritten into URLs that work), you can create a
Junio C Hamanoba4b9282008-07-06 05:20:31604configuration section of the form:</p></div>
Junio C Hamano24bc09a2008-02-28 00:27:44605<div class="listingblock">
606<div class="content">
607<pre><tt> [url "&lt;actual url base&gt;"]
608 insteadOf = &lt;other url base&gt;</tt></pre>
609</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31610<div class="para"><p>For example, with this:</p></div>
Junio C Hamano24bc09a2008-02-28 00:27:44611<div class="listingblock">
612<div class="content">
613<pre><tt> [url "git://git.host.xz/"]
614 insteadOf = host.xz:/path/to/
615 insteadOf = work:</tt></pre>
616</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31617<div class="para"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
618rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p></div>
Junio C Hamano40f2f8d2006-02-07 08:04:39619</div>
Junio C Hamanoba4b9282008-07-06 05:20:31620<h2 id="_remotes_a_id_remotes_a">REMOTES<a id="REMOTES"></a></h2>
Junio C Hamano40f2f8d2006-02-07 08:04:39621<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31622<div class="para"><p>The name of one of the following can be used instead
623of a URL as <tt>&lt;repository&gt;</tt> argument:</p></div>
624<div class="ilist"><ul>
Junio C Hamano054ea082008-06-01 08:26:34625<li>
626<p>
627a remote in the git configuration file: <tt>$GIT_DIR/config</tt>,
628</p>
629</li>
630<li>
631<p>
632a file in the <tt>$GIT_DIR/remotes</tt> directory, or
633</p>
634</li>
635<li>
636<p>
637a file in the <tt>$GIT_DIR/branches</tt> directory.
638</p>
639</li>
Junio C Hamanoba4b9282008-07-06 05:20:31640</ul></div>
641<div class="para"><p>All of these also allow you to omit the refspec from the command line
642because they each contain a refspec which git will use by default.</p></div>
643<h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
644<div class="para"><p>You can choose to provide the name of a remote which you had previously
Junio C Hamano054ea082008-06-01 08:26:34645configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
646or even by a manual edit to the <tt>$GIT_DIR/config</tt> file. The URL of
647this remote will be used to access the repository. The refspec
648of this remote will be used by default when you do
649not provide a refspec on the command line. The entry in the
Junio C Hamanoba4b9282008-07-06 05:20:31650config file would appear like this:</p></div>
Junio C Hamano054ea082008-06-01 08:26:34651<div class="listingblock">
652<div class="content">
653<pre><tt> [remote "&lt;name&gt;"]
654 url = &lt;url&gt;
655 push = &lt;refspec&gt;
656 fetch = &lt;refspec&gt;</tt></pre>
657</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31658<h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
659<div class="para"><p>You can choose to provide the name of a
Junio C Hamano054ea082008-06-01 08:26:34660file in <tt>$GIT_DIR/remotes</tt>. The URL
661in this file will be used to access the repository. The refspec
662in this file will be used as default when you do not
663provide a refspec on the command line. This file should have the
Junio C Hamanoba4b9282008-07-06 05:20:31664following format:</p></div>
Junio C Hamano1caaf472006-12-31 08:29:35665<div class="listingblock">
Junio C Hamano1a4e8412005-12-27 08:17:23666<div class="content">
Junio C Hamanod3361ad2007-01-01 03:20:24667<pre><tt> URL: one of the above URL format
668 Push: &lt;refspec&gt;
669 Pull: &lt;refspec&gt;
670</tt></pre>
Junio C Hamano1a4e8412005-12-27 08:17:23671</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31672<div class="para"><p><tt>Push:</tt> lines are used by <em>git-push</em> and
673<tt>Pull:</tt> lines are used by <em>git-pull</em> and <em>git-fetch</em>.
Junio C Hamano054ea082008-06-01 08:26:34674Multiple <tt>Push:</tt> and <tt>Pull:</tt> lines may
Junio C Hamanoba4b9282008-07-06 05:20:31675be specified for additional branch mappings.</p></div>
676<h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
677<div class="para"><p>You can choose to provide the name of a
Junio C Hamano054ea082008-06-01 08:26:34678file in <tt>$GIT_DIR/branches</tt>.
679The URL in this file will be used to access the repository.
Junio C Hamanoba4b9282008-07-06 05:20:31680This file should have the following format:</p></div>
Junio C Hamano1caaf472006-12-31 08:29:35681<div class="listingblock">
Junio C Hamano249572f2006-10-24 05:44:08682<div class="content">
Junio C Hamano054ea082008-06-01 08:26:34683<pre><tt> &lt;url&gt;#&lt;head&gt;</tt></pre>
Junio C Hamano249572f2006-10-24 05:44:08684</div></div>
Junio C Hamano28363492008-11-14 08:26:31685<div class="para"><p><tt>&lt;url&gt;</tt> is required; <tt>#&lt;head&gt;</tt> is optional.</p></div>
686<div class="para"><p>Depending on the operation, git will use one of the following
687refspecs, if you don't provide one on the command line.
688<tt>&lt;branch&gt;</tt> is the name of this file in <tt>$GIT_DIR/branches</tt> and
689<tt>&lt;head&gt;</tt> defaults to <tt>master</tt>.</p></div>
690<div class="para"><p>git fetch uses:</p></div>
Junio C Hamano1caaf472006-12-31 08:29:35691<div class="listingblock">
Junio C Hamano1a4e8412005-12-27 08:17:23692<div class="content">
Junio C Hamano28363492008-11-14 08:26:31693<pre><tt> refs/heads/&lt;head&gt;:refs/heads/&lt;branch&gt;</tt></pre>
694</div></div>
695<div class="para"><p>git push uses:</p></div>
696<div class="listingblock">
697<div class="content">
698<pre><tt> HEAD:refs/heads/&lt;head&gt;</tt></pre>
Junio C Hamano1a4e8412005-12-27 08:17:23699</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23700</div>
Junio C Hamanoba4b9282008-07-06 05:20:31701<h2 id="_output">OUTPUT</h2>
Junio C Hamano6d559fc2008-02-20 10:44:26702<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31703<div class="para"><p>The output of "git push" depends on the transport method used; this
Junio C Hamano6d559fc2008-02-20 10:44:26704section describes the output when pushing over the git protocol (either
Junio C Hamanoba4b9282008-07-06 05:20:31705locally or via ssh).</p></div>
706<div class="para"><p>The status of the push is output in tabular form, with each line
707representing the status of a single ref. Each line is of the form:</p></div>
Junio C Hamano6d559fc2008-02-20 10:44:26708<div class="listingblock">
709<div class="content">
710<pre><tt> &lt;flag&gt; &lt;summary&gt; &lt;from&gt; -&gt; &lt;to&gt; (&lt;reason&gt;)</tt></pre>
711</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31712<div class="vlist"><dl>
Junio C Hamano6d559fc2008-02-20 10:44:26713<dt>
714flag
715</dt>
716<dd>
717<p>
718 A single character indicating the status of the ref. This is
719 blank for a successfully pushed ref, <tt>!</tt> for a ref that was
720 rejected or failed to push, and <em>=</em> for a ref that was up to
721 date and did not need pushing (note that the status of up to
722 date refs is shown only when <tt>git push</tt> is running verbosely).
723</p>
724</dd>
725<dt>
726summary
727</dt>
728<dd>
729<p>
730 For a successfully pushed ref, the summary shows the old and new
731 values of the ref in a form suitable for using as an argument to
732 <tt>git log</tt> (this is <tt>&lt;old&gt;..&lt;new&gt;</tt> in most cases, and
733 <tt>&lt;old&gt;&#8230;&lt;new&gt;</tt> for forced non-fast forward updates). For a
734 failed update, more details are given for the failure.
735 The string <tt>rejected</tt> indicates that git did not try to send the
736 ref at all (typically because it is not a fast forward). The
737 string <tt>remote rejected</tt> indicates that the remote end refused
738 the update; this rejection is typically caused by a hook on the
739 remote side. The string <tt>remote failure</tt> indicates that the
740 remote end did not report the successful update of the ref
741 (perhaps because of a temporary error on the remote side, a
742 break in the network connection, or other transient error).
743</p>
744</dd>
745<dt>
746from
747</dt>
748<dd>
749<p>
750 The name of the local ref being pushed, minus its
751 <tt>refs/&lt;type&gt;/</tt> prefix. In the case of deletion, the
752 name of the local ref is omitted.
753</p>
754</dd>
755<dt>
756to
757</dt>
758<dd>
759<p>
760 The name of the remote ref being updated, minus its
761 <tt>refs/&lt;type&gt;/</tt> prefix.
762</p>
763</dd>
764<dt>
765reason
766</dt>
767<dd>
768<p>
769 A human-readable explanation. In the case of successfully pushed
770 refs, no explanation is needed. For a failed ref, the reason for
771 failure is described.
772</p>
773</dd>
Junio C Hamanoba4b9282008-07-06 05:20:31774</dl></div>
Junio C Hamano6d559fc2008-02-20 10:44:26775</div>
Junio C Hamanoba4b9282008-07-06 05:20:31776<h2 id="_examples">Examples</h2>
Junio C Hamano6926bef2007-06-16 09:54:05777<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31778<div class="vlist"><dl>
Junio C Hamano6926bef2007-06-16 09:54:05779<dt>
780git push origin master
781</dt>
782<dd>
783<p>
784 Find a ref that matches <tt>master</tt> in the source repository
785 (most likely, it would find <tt>refs/heads/master</tt>), and update
786 the same ref (e.g. <tt>refs/heads/master</tt>) in <tt>origin</tt> repository
Junio C Hamanoa9aee782008-04-23 16:09:20787 with it. If <tt>master</tt> did not exist remotely, it would be
788 created.
Junio C Hamano6926bef2007-06-16 09:54:05789</p>
790</dd>
791<dt>
792git push origin :experimental
793</dt>
794<dd>
795<p>
796 Find a ref that matches <tt>experimental</tt> in the <tt>origin</tt> repository
797 (e.g. <tt>refs/heads/experimental</tt>), and delete it.
798</p>
799</dd>
800<dt>
Junio C Hamano7f80ae82008-07-30 18:31:35801git push origin master:satellite/master dev:satellite/dev
Junio C Hamano6926bef2007-06-16 09:54:05802</dt>
803<dd>
804<p>
Junio C Hamano7f80ae82008-07-30 18:31:35805 Use the source ref that matches <tt>master</tt> (e.g. <tt>refs/heads/master</tt>)
806 to update the ref that matches <tt>satellite/master</tt> (most probably
807 <tt>refs/remotes/satellite/master</tt>) in the <tt>origin</tt> repository, then
808 do the same for <tt>dev</tt> and <tt>satellite/dev</tt>.
Junio C Hamano6926bef2007-06-16 09:54:05809</p>
810</dd>
Junio C Hamanobfd4f9a2007-09-06 08:52:44811<dt>
812git push origin master:refs/heads/experimental
813</dt>
814<dd>
815<p>
816 Create the branch <tt>experimental</tt> in the <tt>origin</tt> repository
Junio C Hamanoa9aee782008-04-23 16:09:20817 by copying the current <tt>master</tt> branch. This form is only
818 needed to create a new branch or tag in the remote repository when
819 the local name and the remote name are different; otherwise,
820 the ref name on its own will work.
Junio C Hamanobfd4f9a2007-09-06 08:52:44821</p>
822</dd>
Junio C Hamanoba4b9282008-07-06 05:20:31823</dl></div>
Junio C Hamano6926bef2007-06-16 09:54:05824</div>
Junio C Hamanoba4b9282008-07-06 05:20:31825<h2 id="_author">Author</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23826<div class="sectionbody">
Junio C Hamano0868a302008-07-22 09:20:44827<div class="para"><p>Written by Junio C Hamano &lt;gitster@pobox.com&gt;, later rewritten in C
Junio C Hamanoba4b9282008-07-06 05:20:31828by Linus Torvalds &lt;torvalds@osdl.org&gt;</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23829</div>
Junio C Hamanoba4b9282008-07-06 05:20:31830<h2 id="_documentation">Documentation</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23831<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31832<div class="para"><p>Documentation by Junio C Hamano and the git-list &lt;git@vger.kernel.org&gt;.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23833</div>
Junio C Hamanoba4b9282008-07-06 05:20:31834<h2 id="_git">GIT</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23835<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31836<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23837</div>
838<div id="footer">
839<div id="footer-text">
Junio C Hamano28363492008-11-14 08:26:31840Last updated 2008-11-14 08:26:10 UTC
Junio C Hamano1a4e8412005-12-27 08:17:23841</div>
842</div>
843</body>
844</html>