1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
\r
6 <meta name="generator" content="AsciiDoc 7.0.1" />
\r
7 <style type="text/css">
\r
9 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
\r
11 border: 1px solid red;
\r
16 margin: 1em 5% 1em 5%;
\r
20 a:visited { color: fuchsia; }
\r
34 h1, h2, h3, h4, h5, h6 {
\r
36 font-family: sans-serif;
\r
38 margin-bottom: 0.5em;
\r
43 border-bottom: 2px solid silver;
\r
46 border-bottom: 2px solid silver;
\r
56 border: 1px solid silver;
\r
61 margin-bottom: 0.5em;
\r
71 font-family: sans-serif;
\r
78 font-family: sans-serif;
\r
82 font-family: sans-serif;
\r
84 border-top: 2px solid silver;
\r
90 padding-bottom: 0.5em;
\r
94 padding-bottom: 0.5em;
\r
98 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
\r
99 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
\r
100 div.admonitionblock {
\r
103 margin-bottom: 1.5em;
\r
105 div.admonitionblock {
\r
107 margin-bottom: 2.5em;
\r
110 div.content { /* Block element content. */
\r
114 /* Block element titles. */
\r
115 div.title, caption.title {
\r
116 font-family: sans-serif;
\r
120 margin-bottom: 0.5em;
\r
126 td div.title:first-child {
\r
129 div.content div.title:first-child {
\r
132 div.content + div.title {
\r
136 div.sidebarblock > div.content {
\r
137 background: #ffffee;
\r
138 border: 1px solid silver;
\r
142 div.listingblock > div.content {
\r
143 border: 1px solid silver;
\r
144 background: #f4f4f4;
\r
148 div.quoteblock > div.content {
\r
149 padding-left: 2.0em;
\r
151 div.quoteblock .attribution {
\r
155 div.admonitionblock .icon {
\r
156 vertical-align: top;
\r
159 text-decoration: underline;
\r
161 padding-right: 0.5em;
\r
163 div.admonitionblock td.content {
\r
164 padding-left: 0.5em;
\r
165 border-left: 2px solid silver;
\r
168 div.exampleblock > div.content {
\r
169 border-left: 2px solid silver;
\r
173 div.verseblock div.content {
\r
177 div.imageblock div.content { padding-left: 0; }
\r
178 div.imageblock img { border: 1px solid silver; }
\r
179 span.image img { border-style: none; }
\r
183 margin-bottom: 0.8em;
\r
188 font-style: italic;
\r
190 dd > *:first-child {
\r
195 list-style-position: outside;
\r
198 list-style-type: lower-alpha;
\r
201 div.tableblock > table {
\r
202 border-color: #527bbd;
\r
206 font-family: sans-serif;
\r
215 margin-bottom: 0.8em;
\r
218 vertical-align: top;
\r
219 font-style: italic;
\r
220 padding-right: 0.8em;
\r
223 vertical-align: top;
\r
227 div#footer-badges { display: none; }
\r
229 include::./stylesheets/xhtml11-manpage.css[]
\r
230 /* Workarounds for IE6's broken and incomplete CSS2. */
\r
232 div.sidebar-content {
\r
233 background: #ffffee;
\r
234 border: 1px solid silver;
\r
237 div.sidebar-title, div.image-title {
\r
238 font-family: sans-serif;
\r
241 margin-bottom: 0.5em;
\r
244 div.listingblock div.content {
\r
245 border: 1px solid silver;
\r
246 background: #f4f4f4;
\r
250 div.quoteblock-content {
\r
251 padding-left: 2.0em;
\r
254 div.exampleblock-content {
\r
255 border-left: 2px solid silver;
\r
256 padding-left: 0.5em;
\r
259 <title>git-push(1)</title>
\r
264 git-push(1) Manual Page
\r
267 <div class="sectionbody">
\r
269 Update remote refs along with associated objects.
\r
274 <div class="sectionbody">
\r
275 <p><em>git-push</em> [--all] [--force] <repository> <refspec>…</p>
\r
277 <h2>DESCRIPTION</h2>
\r
278 <div class="sectionbody">
\r
279 <p>Updates remote refs using local refs, while sending objects
\r
280 necessary to complete the given refs.</p>
\r
281 <p>You can make "interesting" things to happen on the repository
\r
282 every time you push into it, by setting up <em>hooks</em> there. See
\r
283 documentation for <a href="git-receive-pack.html">git-receive-pack(1)</a>.</p>
\r
286 <div class="sectionbody">
\r
293 The "remote" repository that is the source of a fetch
\r
294 or pull operation, or the destination of a push operation.
\r
295 One of the following notations can be used
\r
296 to name the remote repository:
\r
298 <div class="exampleblock">
\r
299 <div class="exampleblock-content">
\r
303 rsync://host.xz/path/to/repo.git/
\r
308 http://host.xz/path/to/repo.git/
\r
313 https://host.xz/path/to/repo.git/
\r
318 git://host.xz/path/to/repo.git/
\r
323 git://host.xz/~user/path/to/repo.git/
\r
328 ssh://host.xz/path/to/repo.git/
\r
333 ssh://host.xz/~user/path/to/repo.git/
\r
338 ssh://host.xz/~/path/to/repo.git
\r
343 <p>SSH Is the default transport protocol and also supports an
\r
344 scp-like syntax. Both syntaxes support username expansion,
\r
345 as does the native git protocol. The following three are
\r
346 identical to the last three above, respectively:</p>
\r
347 <div class="exampleblock">
\r
348 <div class="exampleblock-content">
\r
352 host.xz:/path/to/repo.git/
\r
357 host.xz:~user/path/to/repo.git/
\r
362 host.xz:path/to/repo.git
\r
367 <p>To sync with a local directory, use:</p>
\r
368 <div class="exampleblock">
\r
369 <div class="exampleblock-content">
\r
378 <p>In addition to the above, as a short-hand, the name of a
\r
379 file in <tt>$GIT_DIR/remotes</tt> directory can be given; the
\r
380 named file should be in the following format:</p>
\r
381 <div class="literalblock">
\r
382 <div class="content">
\r
383 <pre><tt>URL: one of the above URL format
\r
384 Push: <refspec>
\r
385 Pull: <refspec></tt></pre>
\r
387 <p>When such a short-hand is specified in place of
\r
388 <repository> without <refspec> parameters on the command
\r
389 line, <refspec> specified on <tt>Push:</tt> lines or <tt>Pull:</tt>
\r
390 lines are used for <tt>git-push</tt> and <tt>git-fetch</tt>/<tt>git-pull</tt>,
\r
391 respectively. Multiple <tt>Push:</tt> and and <tt>Pull:</tt> lines may
\r
392 be specified for additional branch mappings.</p>
\r
393 <p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be
\r
394 specified as an older notation short-hand; the named
\r
395 file should contain a single line, a URL in one of the
\r
396 above formats, optionally followed by a hash <tt>#</tt> and the
\r
397 name of remote head (URL fragment notation).
\r
398 <tt>$GIT_DIR/branches/<remote></tt> file that stores a <url>
\r
399 without the fragment is equivalent to have this in the
\r
400 corresponding file in the <tt>$GIT_DIR/remotes/</tt> directory.</p>
\r
401 <div class="literalblock">
\r
402 <div class="content">
\r
403 <pre><tt>URL: <url>
\r
404 Pull: refs/heads/master:<remote></tt></pre>
\r
406 <p>while having <tt><url>#<head></tt> is equivalent to</p>
\r
407 <div class="literalblock">
\r
408 <div class="content">
\r
409 <pre><tt>URL: <url>
\r
410 Pull: refs/heads/<head>:<remote></tt></pre>
\r
418 The canonical format of a <refspec> parameter is
\r
419 <tt>+?<src>:<dst></tt>; that is, an optional plus <tt>+</tt>, followed
\r
420 by the source ref, followed by a colon <tt>:</tt>, followed by
\r
421 the destination ref.
\r
423 <p>When used in <tt>git-push</tt>, the <src> side can be an
\r
424 arbitrary "SHA1 expression" that can be used as an
\r
425 argument to <tt>git-cat-file -t</tt>. E.g. <tt>master~4</tt> (push
\r
426 four parents before the current master head).</p>
\r
427 <p>For <tt>git-push</tt>, the local ref that matches <src> is used
\r
428 to fast forward the remote ref that matches <dst>. If
\r
429 the optional plus <tt>+</tt> is used, the remote ref is updated
\r
430 even if it does not result in a fast forward update.</p>
\r
431 <p>For <tt>git-fetch</tt> and <tt>git-pull</tt>, the remote ref that matches <src>
\r
432 is fetched, and if <dst> is not empty string, the local
\r
433 ref that matches it is fast forwarded using <src>.
\r
434 Again, if the optional plus <tt>+</tt> is used, the local ref
\r
435 is updated even if it does not result in a fast forward
\r
437 <div class="admonitionblock">
\r
440 <div class="title">Note</div>
\r
442 <td class="content">If the remote branch from which you want to pull is
\r
443 modified in non-linear ways such as being rewound and
\r
444 rebased frequently, then a pull will attempt a merge with
\r
445 an older version of itself, likely conflict, and fail.
\r
446 It is under these conditions that you would want to use
\r
447 the <tt>+</tt> sign to indicate non-fast-forward updates will
\r
448 be needed. There is currently no easy way to determine
\r
449 or declare that a branch will be made available in a
\r
450 repository with this behavior; the pulling user simply
\r
451 must know this is the expected usage pattern for a branch.</td>
\r
454 <div class="admonitionblock">
\r
457 <div class="title">Note</div>
\r
459 <td class="content">You never do your own development on branches that appear
\r
460 on the right hand side of a <refspec> colon on <tt>Pull:</tt> lines;
\r
461 they are to be updated by <tt>git-fetch</tt>. If you intend to do
\r
462 development derived from a remote branch <tt>B</tt>, have a <tt>Pull:</tt>
\r
463 line to track it (i.e. <tt>Pull: B:remote-B</tt>), and have a separate
\r
464 branch <tt>my-B</tt> to do your development on top of it. The latter
\r
465 is created by <tt>git branch my-B remote-B</tt> (or its equivalent <tt>git
\r
466 checkout -b my-B remote-B</tt>). Run <tt>git fetch</tt> to keep track of
\r
467 the progress of the remote side, and when you see something new
\r
468 on the remote branch, merge it into your development branch with
\r
469 <tt>git pull . remote-B</tt>, while you are on <tt>my-B</tt> branch.
\r
470 The common <tt>Pull: master:origin</tt> mapping of a remote <tt>master</tt>
\r
471 branch to a local <tt>origin</tt> branch, which is then merged to a
\r
472 local development branch, again typically named <tt>master</tt>, is made
\r
473 when you run <tt>git clone</tt> for you to follow this pattern.</td>
\r
476 <div class="admonitionblock">
\r
479 <div class="title">Note</div>
\r
481 <td class="content">There is a difference between listing multiple <refspec>
\r
482 directly on <tt>git-pull</tt> command line and having multiple
\r
483 <tt>Pull:</tt> <refspec> lines for a <repository> and running
\r
484 <tt>git-pull</tt> command without any explicit <refspec> parameters.
\r
485 <refspec> listed explicitly on the command line are always
\r
486 merged into the current branch after fetching. In other words,
\r
487 if you list more than one remote refs, you would be making
\r
488 an Octopus. While <tt>git-pull</tt> run without any explicit <refspec>
\r
489 parameter takes default <refspec>s from <tt>Pull:</tt> lines, it
\r
490 merges only the first <refspec> found into the current branch,
\r
491 after fetching all the remote refs. This is because making an
\r
492 Octopus from remote refs is rarely done, while keeping track
\r
493 of multiple remote heads in one-go by fetching more than one
\r
494 is often useful.</td>
\r
497 <p>Some short-cut notations are also supported.</p>
\r
501 For backward compatibility, <tt>tag</tt> is almost ignored;
\r
502 it just makes the following parameter <tag> to mean a
\r
503 refspec <tt>refs/tags/<tag>:refs/tags/<tag></tt>.
\r
508 A parameter <ref> without a colon is equivalent to
\r
509 <ref>: when pulling/fetching, and <ref><tt>:</tt><ref> when
\r
510 pushing. That is, do not store it locally if
\r
511 fetching, and update the same name if pushing.
\r
521 Instead of naming each ref to push, specifies all refs
\r
530 Usually, the command refuses to update a local ref that is
\r
531 not an ancestor of the remote ref used to overwrite it.
\r
532 This flag disables the check. What this means is that the
\r
533 local repository can lose commits; use it with care.
\r
539 <div class="sectionbody">
\r
540 <p>Written by Junio C Hamano <junkio@cox.net></p>
\r
542 <h2>Documentation</h2>
\r
543 <div class="sectionbody">
\r
544 <p>Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
\r
547 <div class="sectionbody">
\r
548 <p>Part of the <a href="git.html">git(7)</a> suite</p>
\r
551 <div id="footer-text">
\r
552 Last updated 27-Dec-2005 00:16:30 PDT
\r