blob: fa25cee08fe371d4ee63c7f9ec183ca4fbd1adb5 [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>
Junio C Hamano9d971152012-12-19 00:43:115<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
6<meta name="generator" content="AsciiDoc 8.6.8" />
Junio C Hamano68cf15a2010-11-06 01:01:597<title>git-merge(1)</title>
Junio C Hamano1a4e8412005-12-27 08:17:238<style type="text/css">
Junio C Hamano9d971152012-12-19 00:43:119/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
10
11/* Default font. */
12body {
13 font-family: Georgia,serif;
14}
15
16/* Title font. */
17h1, h2, h3, h4, h5, h6,
18div.title, caption.title,
19thead, p.table.header,
20#toctitle,
21#author, #revnumber, #revdate, #revremark,
22#footer {
23 font-family: Arial,Helvetica,sans-serif;
Junio C Hamano1a4e8412005-12-27 08:17:2324}
25
26body {
27 margin: 1em 5% 1em 5%;
28}
29
Junio C Hamanoba4b9282008-07-06 05:20:3130a {
31 color: blue;
32 text-decoration: underline;
33}
34a:visited {
35 color: fuchsia;
36}
Junio C Hamano1a4e8412005-12-27 08:17:2337
38em {
39 font-style: italic;
Junio C Hamano68cf15a2010-11-06 01:01:5940 color: navy;
Junio C Hamano1a4e8412005-12-27 08:17:2341}
42
43strong {
44 font-weight: bold;
Junio C Hamano68cf15a2010-11-06 01:01:5945 color: #083194;
Junio C Hamano1a4e8412005-12-27 08:17:2346}
47
Junio C Hamano1a4e8412005-12-27 08:17:2348h1, h2, h3, h4, h5, h6 {
49 color: #527bbd;
Junio C Hamano1a4e8412005-12-27 08:17:2350 margin-top: 1.2em;
51 margin-bottom: 0.5em;
52 line-height: 1.3;
53}
54
Junio C Hamanoba4b9282008-07-06 05:20:3155h1, h2, h3 {
Junio C Hamano1a4e8412005-12-27 08:17:2356 border-bottom: 2px solid silver;
57}
58h2 {
Junio C Hamano1a4e8412005-12-27 08:17:2359 padding-top: 0.5em;
60}
Junio C Hamanoba4b9282008-07-06 05:20:3161h3 {
62 float: left;
63}
64h3 + * {
65 clear: left;
66}
Junio C Hamano9d971152012-12-19 00:43:1167h5 {
68 font-size: 1.0em;
69}
Junio C Hamano1a4e8412005-12-27 08:17:2370
71div.sectionbody {
Junio C Hamano1a4e8412005-12-27 08:17:2372 margin-left: 0;
73}
74
75hr {
76 border: 1px solid silver;
77}
78
79p {
80 margin-top: 0.5em;
81 margin-bottom: 0.5em;
82}
83
Junio C Hamano68cf15a2010-11-06 01:01:5984ul, ol, li > p {
85 margin-top: 0;
86}
Junio C Hamano9d971152012-12-19 00:43:1187ul > li { color: #aaa; }
88ul > li > * { color: black; }
Junio C Hamano68cf15a2010-11-06 01:01:5989
Junio C Hamano9d971152012-12-19 00:43:1190.monospaced, code, pre {
91 font-family: "Courier New", Courier, monospace;
92 font-size: inherit;
93 color: navy;
Junio C Hamano1a4e8412005-12-27 08:17:2394 padding: 0;
95 margin: 0;
96}
97
Junio C Hamano9d971152012-12-19 00:43:1198
99#author {
Junio C Hamano1a4e8412005-12-27 08:17:23100 color: #527bbd;
Junio C Hamano1a4e8412005-12-27 08:17:23101 font-weight: bold;
Junio C Hamanoba4b9282008-07-06 05:20:31102 font-size: 1.1em;
Junio C Hamano1a4e8412005-12-27 08:17:23103}
Junio C Hamano9d971152012-12-19 00:43:11104#email {
Junio C Hamano1a4e8412005-12-27 08:17:23105}
Junio C Hamano9d971152012-12-19 00:43:11106#revnumber, #revdate, #revremark {
Junio C Hamano1a4e8412005-12-27 08:17:23107}
108
Junio C Hamano9d971152012-12-19 00:43:11109#footer {
Junio C Hamano1a4e8412005-12-27 08:17:23110 font-size: small;
111 border-top: 2px solid silver;
112 padding-top: 0.5em;
113 margin-top: 4.0em;
114}
Junio C Hamano9d971152012-12-19 00:43:11115#footer-text {
Junio C Hamano1a4e8412005-12-27 08:17:23116 float: left;
117 padding-bottom: 0.5em;
118}
Junio C Hamano9d971152012-12-19 00:43:11119#footer-badges {
Junio C Hamano1a4e8412005-12-27 08:17:23120 float: right;
121 padding-bottom: 0.5em;
122}
123
Junio C Hamano9d971152012-12-19 00:43:11124#preamble {
Junio C Hamano68cf15a2010-11-06 01:01:59125 margin-top: 1.5em;
126 margin-bottom: 1.5em;
127}
Junio C Hamano9d971152012-12-19 00:43:11128div.imageblock, div.exampleblock, div.verseblock,
Junio C Hamano1a4e8412005-12-27 08:17:23129div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
130div.admonitionblock {
Junio C Hamano7bd050f2011-09-22 06:32:22131 margin-top: 1.0em;
Junio C Hamano1a4e8412005-12-27 08:17:23132 margin-bottom: 1.5em;
133}
134div.admonitionblock {
Junio C Hamano7bd050f2011-09-22 06:32:22135 margin-top: 2.0em;
136 margin-bottom: 2.0em;
137 margin-right: 10%;
138 color: #606060;
Junio C Hamano1a4e8412005-12-27 08:17:23139}
140
141div.content { /* Block element content. */
142 padding: 0;
143}
144
145/* Block element titles. */
146div.title, caption.title {
Junio C Hamano68cf15a2010-11-06 01:01:59147 color: #527bbd;
Junio C Hamano1a4e8412005-12-27 08:17:23148 font-weight: bold;
149 text-align: left;
150 margin-top: 1.0em;
151 margin-bottom: 0.5em;
152}
153div.title + * {
154 margin-top: 0;
155}
156
157td div.title:first-child {
158 margin-top: 0.0em;
159}
160div.content div.title:first-child {
161 margin-top: 0.0em;
162}
163div.content + div.title {
164 margin-top: 0.0em;
165}
166
167div.sidebarblock > div.content {
168 background: #ffffee;
Junio C Hamano9d971152012-12-19 00:43:11169 border: 1px solid #dddddd;
170 border-left: 4px solid #f0f0f0;
Junio C Hamano1a4e8412005-12-27 08:17:23171 padding: 0.5em;
172}
173
174div.listingblock > div.content {
Junio C Hamano9d971152012-12-19 00:43:11175 border: 1px solid #dddddd;
176 border-left: 5px solid #f0f0f0;
177 background: #f8f8f8;
Junio C Hamano1a4e8412005-12-27 08:17:23178 padding: 0.5em;
179}
180
Junio C Hamano7bd050f2011-09-22 06:32:22181div.quoteblock, div.verseblock {
182 padding-left: 1.0em;
183 margin-left: 1.0em;
Junio C Hamano68cf15a2010-11-06 01:01:59184 margin-right: 10%;
Junio C Hamano9d971152012-12-19 00:43:11185 border-left: 5px solid #f0f0f0;
186 color: #888;
Junio C Hamano1a4e8412005-12-27 08:17:23187}
Junio C Hamano7bd050f2011-09-22 06:32:22188
Junio C Hamano68cf15a2010-11-06 01:01:59189div.quoteblock > div.attribution {
190 padding-top: 0.5em;
Junio C Hamano1a4e8412005-12-27 08:17:23191 text-align: right;
192}
Junio C Hamano68cf15a2010-11-06 01:01:59193
Junio C Hamano9d971152012-12-19 00:43:11194div.verseblock > pre.content {
195 font-family: inherit;
196 font-size: inherit;
Junio C Hamano68cf15a2010-11-06 01:01:59197}
198div.verseblock > div.attribution {
199 padding-top: 0.75em;
200 text-align: left;
201}
202/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
Junio C Hamanoba4b9282008-07-06 05:20:31203div.verseblock + div.attribution {
204 text-align: left;
205}
Junio C Hamano1a4e8412005-12-27 08:17:23206
207div.admonitionblock .icon {
208 vertical-align: top;
209 font-size: 1.1em;
210 font-weight: bold;
211 text-decoration: underline;
212 color: #527bbd;
213 padding-right: 0.5em;
214}
215div.admonitionblock td.content {
216 padding-left: 0.5em;
Junio C Hamano7bd050f2011-09-22 06:32:22217 border-left: 3px solid #dddddd;
Junio C Hamano1a4e8412005-12-27 08:17:23218}
219
220div.exampleblock > div.content {
Junio C Hamano7bd050f2011-09-22 06:32:22221 border-left: 3px solid #dddddd;
222 padding-left: 0.5em;
Junio C Hamano1a4e8412005-12-27 08:17:23223}
224
Junio C Hamano1a4e8412005-12-27 08:17:23225div.imageblock div.content { padding-left: 0; }
Junio C Hamano1a4e8412005-12-27 08:17:23226span.image img { border-style: none; }
Junio C Hamano68cf15a2010-11-06 01:01:59227a.image:visited { color: white; }
Junio C Hamano1a4e8412005-12-27 08:17:23228
229dl {
230 margin-top: 0.8em;
231 margin-bottom: 0.8em;
232}
233dt {
234 margin-top: 0.5em;
235 margin-bottom: 0;
Junio C Hamano68cf15a2010-11-06 01:01:59236 font-style: normal;
237 color: navy;
Junio C Hamano1a4e8412005-12-27 08:17:23238}
239dd > *:first-child {
Junio C Hamano68cf15a2010-11-06 01:01:59240 margin-top: 0.1em;
Junio C Hamano1a4e8412005-12-27 08:17:23241}
242
243ul, ol {
244 list-style-position: outside;
245}
Junio C Hamano68cf15a2010-11-06 01:01:59246ol.arabic {
247 list-style-type: decimal;
248}
249ol.loweralpha {
Junio C Hamano1a4e8412005-12-27 08:17:23250 list-style-type: lower-alpha;
251}
Junio C Hamano68cf15a2010-11-06 01:01:59252ol.upperalpha {
253 list-style-type: upper-alpha;
254}
255ol.lowerroman {
256 list-style-type: lower-roman;
257}
258ol.upperroman {
259 list-style-type: upper-roman;
260}
261
262div.compact ul, div.compact ol,
263div.compact p, div.compact p,
264div.compact div, div.compact div {
265 margin-top: 0.1em;
266 margin-bottom: 0.1em;
267}
Junio C Hamano1a4e8412005-12-27 08:17:23268
Junio C Hamano1a4e8412005-12-27 08:17:23269tfoot {
270 font-weight: bold;
271}
Junio C Hamano68cf15a2010-11-06 01:01:59272td > div.verse {
273 white-space: pre;
274}
Junio C Hamano68cf15a2010-11-06 01:01:59275
276div.hdlist {
Junio C Hamano1a4e8412005-12-27 08:17:23277 margin-top: 0.8em;
278 margin-bottom: 0.8em;
279}
Junio C Hamano68cf15a2010-11-06 01:01:59280div.hdlist tr {
281 padding-bottom: 15px;
Junio C Hamanoba4b9282008-07-06 05:20:31282}
Junio C Hamano68cf15a2010-11-06 01:01:59283dt.hdlist1.strong, td.hdlist1.strong {
284 font-weight: bold;
285}
286td.hdlist1 {
Junio C Hamano1a4e8412005-12-27 08:17:23287 vertical-align: top;
Junio C Hamano68cf15a2010-11-06 01:01:59288 font-style: normal;
Junio C Hamano1a4e8412005-12-27 08:17:23289 padding-right: 0.8em;
Junio C Hamano68cf15a2010-11-06 01:01:59290 color: navy;
Junio C Hamano1a4e8412005-12-27 08:17:23291}
Junio C Hamano68cf15a2010-11-06 01:01:59292td.hdlist2 {
Junio C Hamano1a4e8412005-12-27 08:17:23293 vertical-align: top;
294}
Junio C Hamano68cf15a2010-11-06 01:01:59295div.hdlist.compact tr {
296 margin: 0;
297 padding-bottom: 0;
298}
299
300.comment {
301 background: yellow;
302}
Junio C Hamano1a4e8412005-12-27 08:17:23303
Junio C Hamano7bd050f2011-09-22 06:32:22304.footnote, .footnoteref {
305 font-size: 0.8em;
306}
307
308span.footnote, span.footnoteref {
309 vertical-align: super;
310}
311
312#footnotes {
313 margin: 20px 0 20px 0;
314 padding: 7px 0 0 0;
315}
316
317#footnotes div.footnote {
318 margin: 0 0 5px 0;
319}
320
321#footnotes hr {
322 border: none;
323 border-top: 1px solid silver;
324 height: 1px;
325 text-align: left;
326 margin-left: 0;
327 width: 20%;
328 min-width: 100px;
329}
330
Junio C Hamano9d971152012-12-19 00:43:11331div.colist td {
332 padding-right: 0.5em;
333 padding-bottom: 0.3em;
334 vertical-align: top;
335}
336div.colist td img {
337 margin-top: 0.3em;
Junio C Hamano1a4e8412005-12-27 08:17:23338}
Junio C Hamanoba4b9282008-07-06 05:20:31339
Junio C Hamano9d971152012-12-19 00:43:11340@media print {
341 #footer-badges { display: none; }
342}
343
344#toc {
Junio C Hamano7bd050f2011-09-22 06:32:22345 margin-bottom: 2.5em;
346}
347
Junio C Hamano9d971152012-12-19 00:43:11348#toctitle {
Junio C Hamanoba4b9282008-07-06 05:20:31349 color: #527bbd;
Junio C Hamanoba4b9282008-07-06 05:20:31350 font-size: 1.1em;
351 font-weight: bold;
352 margin-top: 1.0em;
353 margin-bottom: 0.1em;
354}
355
Junio C Hamano9d971152012-12-19 00:43:11356div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
Junio C Hamanoba4b9282008-07-06 05:20:31357 margin-top: 0;
358 margin-bottom: 0;
359}
360div.toclevel2 {
361 margin-left: 2em;
362 font-size: 0.9em;
363}
364div.toclevel3 {
365 margin-left: 4em;
366 font-size: 0.9em;
367}
368div.toclevel4 {
369 margin-left: 6em;
370 font-size: 0.9em;
371}
Junio C Hamano9d971152012-12-19 00:43:11372
373span.aqua { color: aqua; }
374span.black { color: black; }
375span.blue { color: blue; }
376span.fuchsia { color: fuchsia; }
377span.gray { color: gray; }
378span.green { color: green; }
379span.lime { color: lime; }
380span.maroon { color: maroon; }
381span.navy { color: navy; }
382span.olive { color: olive; }
383span.purple { color: purple; }
384span.red { color: red; }
385span.silver { color: silver; }
386span.teal { color: teal; }
387span.white { color: white; }
388span.yellow { color: yellow; }
389
390span.aqua-background { background: aqua; }
391span.black-background { background: black; }
392span.blue-background { background: blue; }
393span.fuchsia-background { background: fuchsia; }
394span.gray-background { background: gray; }
395span.green-background { background: green; }
396span.lime-background { background: lime; }
397span.maroon-background { background: maroon; }
398span.navy-background { background: navy; }
399span.olive-background { background: olive; }
400span.purple-background { background: purple; }
401span.red-background { background: red; }
402span.silver-background { background: silver; }
403span.teal-background { background: teal; }
404span.white-background { background: white; }
405span.yellow-background { background: yellow; }
406
407span.big { font-size: 2em; }
408span.small { font-size: 0.6em; }
409
410span.underline { text-decoration: underline; }
411span.overline { text-decoration: overline; }
412span.line-through { text-decoration: line-through; }
413
414div.unbreakable { page-break-inside: avoid; }
415
416
417/*
418 * xhtml11 specific
419 *
420 * */
421
422div.tableblock {
423 margin-top: 1.0em;
424 margin-bottom: 1.5em;
425}
426div.tableblock > table {
427 border: 3px solid #527bbd;
428}
429thead, p.table.header {
430 font-weight: bold;
431 color: #527bbd;
432}
433p.table {
434 margin-top: 0;
435}
436/* Because the table frame attribute is overriden by CSS in most browsers. */
437div.tableblock > table[frame="void"] {
438 border-style: none;
439}
440div.tableblock > table[frame="hsides"] {
441 border-left-style: none;
442 border-right-style: none;
443}
444div.tableblock > table[frame="vsides"] {
445 border-top-style: none;
446 border-bottom-style: none;
447}
448
449
450/*
451 * html5 specific
452 *
453 * */
454
455table.tableblock {
456 margin-top: 1.0em;
457 margin-bottom: 1.5em;
458}
459thead, p.tableblock.header {
460 font-weight: bold;
461 color: #527bbd;
462}
463p.tableblock {
464 margin-top: 0;
465}
466table.tableblock {
467 border-width: 3px;
468 border-spacing: 0px;
469 border-style: solid;
470 border-color: #527bbd;
471 border-collapse: collapse;
472}
473th.tableblock, td.tableblock {
474 border-width: 1px;
475 padding: 4px;
476 border-style: solid;
477 border-color: #527bbd;
478}
479
480table.tableblock.frame-topbot {
481 border-left-style: hidden;
482 border-right-style: hidden;
483}
484table.tableblock.frame-sides {
485 border-top-style: hidden;
486 border-bottom-style: hidden;
487}
488table.tableblock.frame-none {
489 border-style: hidden;
490}
491
492th.tableblock.halign-left, td.tableblock.halign-left {
493 text-align: left;
494}
495th.tableblock.halign-center, td.tableblock.halign-center {
496 text-align: center;
497}
498th.tableblock.halign-right, td.tableblock.halign-right {
499 text-align: right;
500}
501
502th.tableblock.valign-top, td.tableblock.valign-top {
503 vertical-align: top;
504}
505th.tableblock.valign-middle, td.tableblock.valign-middle {
506 vertical-align: middle;
507}
508th.tableblock.valign-bottom, td.tableblock.valign-bottom {
509 vertical-align: bottom;
510}
511
512
513/*
514 * manpage specific
515 *
516 * */
517
518body.manpage h1 {
Junio C Hamano68cf15a2010-11-06 01:01:59519 padding-top: 0.5em;
520 padding-bottom: 0.5em;
521 border-top: 2px solid silver;
522 border-bottom: 2px solid silver;
523}
Junio C Hamano9d971152012-12-19 00:43:11524body.manpage h2 {
Junio C Hamano68cf15a2010-11-06 01:01:59525 border-style: none;
526}
Junio C Hamano9d971152012-12-19 00:43:11527body.manpage div.sectionbody {
528 margin-left: 3em;
Junio C Hamano68cf15a2010-11-06 01:01:59529}
530
531@media print {
Junio C Hamano9d971152012-12-19 00:43:11532 body.manpage div#toc { display: none; }
Junio C Hamano68cf15a2010-11-06 01:01:59533}
534
Junio C Hamano1a4e8412005-12-27 08:17:23535
Junio C Hamano1a4e8412005-12-27 08:17:23536</style>
Junio C Hamano7bd050f2011-09-22 06:32:22537<script type="text/javascript">
538/*<![CDATA[*/
Junio C Hamano7bd050f2011-09-22 06:32:22539var asciidoc = { // Namespace.
540
541/////////////////////////////////////////////////////////////////////
542// Table Of Contents generator
543/////////////////////////////////////////////////////////////////////
544
545/* Author: Mihai Bazon, September 2002
546 * http://students.infoiasi.ro/~mishoo
547 *
548 * Table Of Content generator
549 * Version: 0.4
550 *
551 * Feel free to use this script under the terms of the GNU General Public
552 * License, as long as you do not remove or alter this notice.
553 */
554
555 /* modified by Troy D. Hanson, September 2006. License: GPL */
556 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
557
558// toclevels = 1..4.
559toc: function (toclevels) {
560
561 function getText(el) {
562 var text = "";
563 for (var i = el.firstChild; i != null; i = i.nextSibling) {
564 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
565 text += i.data;
566 else if (i.firstChild != null)
567 text += getText(i);
568 }
569 return text;
570 }
571
572 function TocEntry(el, text, toclevel) {
573 this.element = el;
574 this.text = text;
575 this.toclevel = toclevel;
576 }
577
578 function tocEntries(el, toclevels) {
579 var result = new Array;
Junio C Hamano9d971152012-12-19 00:43:11580 var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
Junio C Hamano7bd050f2011-09-22 06:32:22581 // Function that scans the DOM tree for header elements (the DOM2
582 // nodeIterator API would be a better technique but not supported by all
583 // browsers).
584 var iterate = function (el) {
585 for (var i = el.firstChild; i != null; i = i.nextSibling) {
586 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
587 var mo = re.exec(i.tagName);
588 if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
589 result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
590 }
591 iterate(i);
592 }
593 }
594 }
595 iterate(el);
596 return result;
597 }
598
599 var toc = document.getElementById("toc");
Junio C Hamano9d971152012-12-19 00:43:11600 if (!toc) {
601 return;
602 }
603
604 // Delete existing TOC entries in case we're reloading the TOC.
605 var tocEntriesToRemove = [];
606 var i;
607 for (i = 0; i < toc.childNodes.length; i++) {
608 var entry = toc.childNodes[i];
609 if (entry.nodeName.toLowerCase() == 'div'
610 && entry.getAttribute("class")
611 && entry.getAttribute("class").match(/^toclevel/))
612 tocEntriesToRemove.push(entry);
613 }
614 for (i = 0; i < tocEntriesToRemove.length; i++) {
615 toc.removeChild(tocEntriesToRemove[i]);
616 }
617
618 // Rebuild TOC entries.
Junio C Hamano7bd050f2011-09-22 06:32:22619 var entries = tocEntries(document.getElementById("content"), toclevels);
620 for (var i = 0; i < entries.length; ++i) {
621 var entry = entries[i];
622 if (entry.element.id == "")
623 entry.element.id = "_toc_" + i;
624 var a = document.createElement("a");
625 a.href = "#" + entry.element.id;
626 a.appendChild(document.createTextNode(entry.text));
627 var div = document.createElement("div");
628 div.appendChild(a);
629 div.className = "toclevel" + entry.toclevel;
630 toc.appendChild(div);
631 }
632 if (entries.length == 0)
633 toc.parentNode.removeChild(toc);
634},
635
636
637/////////////////////////////////////////////////////////////////////
638// Footnotes generator
639/////////////////////////////////////////////////////////////////////
640
641/* Based on footnote generation code from:
642 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
643 */
644
645footnotes: function () {
Junio C Hamano9d971152012-12-19 00:43:11646 // Delete existing footnote entries in case we're reloading the footnodes.
647 var i;
Junio C Hamano7bd050f2011-09-22 06:32:22648 var noteholder = document.getElementById("footnotes");
Junio C Hamano9d971152012-12-19 00:43:11649 if (!noteholder) {
650 return;
651 }
652 var entriesToRemove = [];
653 for (i = 0; i < noteholder.childNodes.length; i++) {
654 var entry = noteholder.childNodes[i];
655 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
656 entriesToRemove.push(entry);
657 }
658 for (i = 0; i < entriesToRemove.length; i++) {
659 noteholder.removeChild(entriesToRemove[i]);
660 }
661
662 // Rebuild footnote entries.
663 var cont = document.getElementById("content");
Junio C Hamano7bd050f2011-09-22 06:32:22664 var spans = cont.getElementsByTagName("span");
665 var refs = {};
666 var n = 0;
667 for (i=0; i<spans.length; i++) {
668 if (spans[i].className == "footnote") {
669 n++;
Junio C Hamano9d971152012-12-19 00:43:11670 var note = spans[i].getAttribute("data-note");
671 if (!note) {
672 // Use [\s\S] in place of . so multi-line matches work.
673 // Because JavaScript has no s (dotall) regex flag.
674 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
675 spans[i].innerHTML =
676 "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
677 "' title='View footnote' class='footnote'>" + n + "</a>]";
678 spans[i].setAttribute("data-note", note);
679 }
Junio C Hamano7bd050f2011-09-22 06:32:22680 noteholder.innerHTML +=
681 "<div class='footnote' id='_footnote_" + n + "'>" +
682 "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
683 n + "</a>. " + note + "</div>";
Junio C Hamano7bd050f2011-09-22 06:32:22684 var id =spans[i].getAttribute("id");
685 if (id != null) refs["#"+id] = n;
686 }
687 }
688 if (n == 0)
689 noteholder.parentNode.removeChild(noteholder);
690 else {
691 // Process footnoterefs.
692 for (i=0; i<spans.length; i++) {
693 if (spans[i].className == "footnoteref") {
694 var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
695 href = href.match(/#.*/)[0]; // Because IE return full URL.
696 n = refs[href];
697 spans[i].innerHTML =
698 "[<a href='#_footnote_" + n +
699 "' title='View footnote' class='footnote'>" + n + "</a>]";
700 }
701 }
702 }
Junio C Hamano9d971152012-12-19 00:43:11703},
704
705install: function(toclevels) {
706 var timerId;
707
708 function reinstall() {
709 asciidoc.footnotes();
710 if (toclevels) {
711 asciidoc.toc(toclevels);
712 }
713 }
714
715 function reinstallAndRemoveTimer() {
716 clearInterval(timerId);
717 reinstall();
718 }
719
720 timerId = setInterval(reinstall, 500);
721 if (document.addEventListener)
722 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
723 else
724 window.onload = reinstallAndRemoveTimer;
Junio C Hamano7bd050f2011-09-22 06:32:22725}
726
727}
Junio C Hamano9d971152012-12-19 00:43:11728asciidoc.install();
Junio C Hamano7bd050f2011-09-22 06:32:22729/*]]>*/
730</script>
Junio C Hamano1a4e8412005-12-27 08:17:23731</head>
Junio C Hamano9d971152012-12-19 00:43:11732<body class="manpage">
Junio C Hamano1a4e8412005-12-27 08:17:23733<div id="header">
734<h1>
735git-merge(1) Manual Page
736</h1>
737<h2>NAME</h2>
738<div class="sectionbody">
739<p>git-merge -
Junio C Hamano7c73c662007-01-19 00:37:50740 Join two or more development histories together
Junio C Hamano1a4e8412005-12-27 08:17:23741</p>
742</div>
743</div>
Junio C Hamano7bd050f2011-09-22 06:32:22744<div id="content">
Junio C Hamano9d971152012-12-19 00:43:11745<div class="sect1">
Junio C Hamano68cf15a2010-11-06 01:01:59746<h2 id="_synopsis">SYNOPSIS</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23747<div class="sectionbody">
Junio C Hamanoee6d9612006-11-27 20:03:22748<div class="verseblock">
Junio C Hamano9d971152012-12-19 00:43:11749<pre class="content"><em>git merge</em> [-n] [--stat] [--no-commit] [--squash] [--[no-]edit]
Junio C Hamanob04bb3f2010-04-14 14:07:36750 [-s &lt;strategy&gt;] [-X &lt;strategy-option&gt;]
Junio C Hamanoa03ac862011-04-02 04:32:29751 [--[no-]rerere-autoupdate] [-m &lt;msg&gt;] [&lt;commit&gt;&#8230;]
Junio C Hamano788eeba2010-12-08 22:50:43752<em>git merge</em> &lt;msg&gt; HEAD &lt;commit&gt;&#8230;
Junio C Hamano9d971152012-12-19 00:43:11753<em>git merge</em> --abort</pre>
754<div class="attribution">
Junio C Hamano68cf15a2010-11-06 01:01:59755</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23756</div>
Junio C Hamano9d971152012-12-19 00:43:11757</div>
758<div class="sect1">
Junio C Hamanoba4b9282008-07-06 05:20:31759<h2 id="_description">DESCRIPTION</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23760<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:59761<div class="paragraph"><p>Incorporates changes from the named commits (since the time their
Junio C Hamanod0d892c2010-01-24 20:06:29762histories diverged from the current branch) into the current
763branch. This command is used by <em>git pull</em> to incorporate changes
764from another repository and can be used by hand to merge changes
765from one branch into another.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:59766<div class="paragraph"><p>Assume the following history exists and the current branch is
Junio C Hamano9d971152012-12-19 00:43:11767"<code>master</code>":</p></div>
Junio C Hamanod0d892c2010-01-24 20:06:29768<div class="listingblock">
769<div class="content">
Junio C Hamano9d971152012-12-19 00:43:11770<pre><code> A---B---C topic
Junio C Hamanod0d892c2010-01-24 20:06:29771 /
Junio C Hamano9d971152012-12-19 00:43:11772 D---E---F---G master</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:29773</div></div>
Junio C Hamano9d971152012-12-19 00:43:11774<div class="paragraph"><p>Then "<code>git merge topic</code>" will replay the changes made on the
775<code>topic</code> branch since it diverged from <code>master</code> (i.e., <code>E</code>) until
776its current commit (<code>C</code>) on top of <code>master</code>, and record the result
Junio C Hamanod0d892c2010-01-24 20:06:29777in a new commit along with the names of the two parent commits and
778a log message from the user describing the changes.</p></div>
779<div class="listingblock">
780<div class="content">
Junio C Hamano9d971152012-12-19 00:43:11781<pre><code> A---B---C topic
Junio C Hamanod0d892c2010-01-24 20:06:29782 / \
Junio C Hamano9d971152012-12-19 00:43:11783 D---E---F---G---H master</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:29784</div></div>
Junio C Hamano9d971152012-12-19 00:43:11785<div class="paragraph"><p>The second syntax (&lt;msg&gt; <code>HEAD</code> &lt;commit&gt;&#8230;) is supported for
Junio C Hamano1974bf22007-10-31 05:57:20786historical reasons. Do not use it from the command line or in
Junio C Hamano9d971152012-12-19 00:43:11787new scripts. It is the same as <code>git merge -m &lt;msg&gt; &lt;commit&gt;...</code>.</p></div>
788<div class="paragraph"><p>The third syntax ("<code>git merge --abort</code>") can only be run after the
Junio C Hamano788eeba2010-12-08 22:50:43789merge has resulted in conflicts. <em>git merge --abort</em> will abort the
790merge process and try to reconstruct the pre-merge state. However,
791if there were uncommitted changes when the merge started (and
792especially if those changes were further modified after the merge
793was started), <em>git merge --abort</em> will in some cases be unable to
794reconstruct the original (pre-merge) changes. Therefore:</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:59795<div class="paragraph"><p><strong>Warning</strong>: Running <em>git merge</em> with uncommitted changes is
Junio C Hamano1aa40d22010-01-21 17:46:43796discouraged: while possible, it leaves you in a state that is hard to
797back out of in the case of a conflict.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23798</div>
Junio C Hamano9d971152012-12-19 00:43:11799</div>
800<div class="sect1">
Junio C Hamanoba4b9282008-07-06 05:20:31801<h2 id="_options">OPTIONS</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23802<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:59803<div class="dlist"><dl>
804<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55805--commit
806</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59807<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55808--no-commit
809</dt>
810<dd>
811<p>
812 Perform the merge and commit the result. This option can
813 be used to override --no-commit.
814</p>
Junio C Hamano68cf15a2010-11-06 01:01:59815<div class="paragraph"><p>With --no-commit perform the merge but pretend the merge
Junio C Hamanoc21ab052009-10-31 04:03:55816failed and do not autocommit, to give the user a chance to
817inspect and further tweak the merge result before committing.</p></div>
818</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59819<dt class="hdlist1">
Junio C Hamano11821ed2011-10-19 18:42:09820--edit
821</dt>
822<dt class="hdlist1">
Junio C Hamano795a5a32012-02-02 01:36:37823--no-edit
Junio C Hamano11821ed2011-10-19 18:42:09824</dt>
825<dd>
Junio C Hamano92887a32011-12-07 00:26:29826<p>
Junio C Hamano795a5a32012-02-02 01:36:37827 Invoke an editor before committing successful mechanical merge to
828 further edit the auto-generated merge message, so that the user
Junio C Hamano9d971152012-12-19 00:43:11829 can explain and justify the merge. The <code>--no-edit</code> option can be
Junio C Hamano795a5a32012-02-02 01:36:37830 used to accept the auto-generated message (this is generally
Junio C Hamano9d971152012-12-19 00:43:11831 discouraged). The <code>--edit</code> option is still useful if you are
832 giving a draft message with the <code>-m</code> option from the command line
Junio C Hamano795a5a32012-02-02 01:36:37833 and want to edit it in the editor.
Junio C Hamano92887a32011-12-07 00:26:29834</p>
Junio C Hamano795a5a32012-02-02 01:36:37835<div class="paragraph"><p>Older scripts may depend on the historical behaviour of not allowing the
836user to edit the merge log message. They will see an editor opened when
Junio C Hamano9d971152012-12-19 00:43:11837they run <code>git merge</code>. To make it easier to adjust such scripts to the
838updated behaviour, the environment variable <code>GIT_MERGE_AUTOEDIT</code> can be
839set to <code>no</code> at the beginning of them.</p></div>
Junio C Hamano11821ed2011-10-19 18:42:09840</dd>
841<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55842--ff
843</dt>
Junio C Hamanof54f08e2012-02-27 07:49:19844<dd>
845<p>
846 When the merge resolves as a fast-forward, only update the branch
847 pointer, without creating a merge commit. This is the default
848 behavior.
849</p>
850</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59851<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55852--no-ff
853</dt>
854<dd>
855<p>
Junio C Hamanof54f08e2012-02-27 07:49:19856 Create a merge commit even when the merge resolves as a
857 fast-forward.
Junio C Hamanoc21ab052009-10-31 04:03:55858</p>
Junio C Hamanof54f08e2012-02-27 07:49:19859</dd>
860<dt class="hdlist1">
861--ff-only
862</dt>
863<dd>
864<p>
865 Refuse to merge and exit with a non-zero status unless the
Junio C Hamano9d971152012-12-19 00:43:11866 current <code>HEAD</code> is already up-to-date or the merge can be
Junio C Hamanof54f08e2012-02-27 07:49:19867 resolved as a fast-forward.
868</p>
Junio C Hamanoc21ab052009-10-31 04:03:55869</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59870<dt class="hdlist1">
Junio C Hamano3b4609d2010-09-30 00:04:34871--log[=&lt;n&gt;]
Junio C Hamanoc21ab052009-10-31 04:03:55872</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59873<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55874--no-log
875</dt>
876<dd>
877<p>
878 In addition to branch names, populate the log message with
Junio C Hamano3b4609d2010-09-30 00:04:34879 one-line descriptions from at most &lt;n&gt; actual commits that are being
Junio C Hamanoa28a9202012-06-21 07:08:23880 merged. See also <a href="git-fmt-merge-msg.html">git-fmt-merge-msg(1)</a>.
Junio C Hamanoc21ab052009-10-31 04:03:55881</p>
Junio C Hamano68cf15a2010-11-06 01:01:59882<div class="paragraph"><p>With --no-log do not list one-line descriptions from the
Junio C Hamanoc21ab052009-10-31 04:03:55883actual commits being merged.</p></div>
884</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59885<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55886--stat
887</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59888<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55889-n
890</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59891<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55892--no-stat
893</dt>
894<dd>
895<p>
896 Show a diffstat at the end of the merge. The diffstat is also
897 controlled by the configuration option merge.stat.
898</p>
Junio C Hamano68cf15a2010-11-06 01:01:59899<div class="paragraph"><p>With -n or --no-stat do not show a diffstat at the end of the
Junio C Hamanoc21ab052009-10-31 04:03:55900merge.</p></div>
901</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59902<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55903--squash
904</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59905<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55906--no-squash
907</dt>
908<dd>
909<p>
910 Produce the working tree and index state as if a real
911 merge happened (except for the merge information),
912 but do not actually make a commit or
Junio C Hamano9d971152012-12-19 00:43:11913 move the <code>HEAD</code>, nor record <code>$GIT_DIR/MERGE_HEAD</code> to
914 cause the next <code>git commit</code> command to create a merge
Junio C Hamanoc21ab052009-10-31 04:03:55915 commit. This allows you to create a single commit on
916 top of the current branch whose effect is the same as
917 merging another branch (or more in case of an octopus).
918</p>
Junio C Hamano68cf15a2010-11-06 01:01:59919<div class="paragraph"><p>With --no-squash perform the merge and commit the result. This
Junio C Hamanoc21ab052009-10-31 04:03:55920option can be used to override --squash.</p></div>
921</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59922<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55923-s &lt;strategy&gt;
924</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59925<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55926--strategy=&lt;strategy&gt;
927</dt>
928<dd>
929<p>
930 Use the given merge strategy; can be supplied more than
931 once to specify them in the order they should be tried.
Junio C Hamano9d971152012-12-19 00:43:11932 If there is no <code>-s</code> option, a built-in list of strategies
Junio C Hamano1aa40d22010-01-21 17:46:43933 is used instead (<em>git merge-recursive</em> when merging a single
934 head, <em>git merge-octopus</em> otherwise).
Junio C Hamanoc21ab052009-10-31 04:03:55935</p>
936</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59937<dt class="hdlist1">
Junio C Hamanob04bb3f2010-04-14 14:07:36938-X &lt;option&gt;
939</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59940<dt class="hdlist1">
Junio C Hamanob04bb3f2010-04-14 14:07:36941--strategy-option=&lt;option&gt;
942</dt>
943<dd>
944<p>
945 Pass merge strategy specific option through to the merge
946 strategy.
947</p>
948</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59949<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55950--summary
951</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59952<dt class="hdlist1">
Junio C Hamanoc21ab052009-10-31 04:03:55953--no-summary
954</dt>
955<dd>
956<p>
957 Synonyms to --stat and --no-stat; these are deprecated and will be
958 removed in the future.
959</p>
960</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59961<dt class="hdlist1">
Junio C Hamano610d1762008-11-28 06:27:13962-q
963</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59964<dt class="hdlist1">
Junio C Hamano610d1762008-11-28 06:27:13965--quiet
966</dt>
967<dd>
968<p>
Junio C Hamanod2c978f2011-03-20 19:42:22969 Operate quietly. Implies --no-progress.
Junio C Hamano610d1762008-11-28 06:27:13970</p>
971</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59972<dt class="hdlist1">
Junio C Hamano610d1762008-11-28 06:27:13973-v
974</dt>
Junio C Hamano68cf15a2010-11-06 01:01:59975<dt class="hdlist1">
Junio C Hamano610d1762008-11-28 06:27:13976--verbose
977</dt>
978<dd>
979<p>
980 Be verbose.
981</p>
982</dd>
Junio C Hamano68cf15a2010-11-06 01:01:59983<dt class="hdlist1">
Junio C Hamanod2c978f2011-03-20 19:42:22984--progress
985</dt>
986<dt class="hdlist1">
987--no-progress
988</dt>
989<dd>
990<p>
991 Turn progress on/off explicitly. If neither is specified,
992 progress is shown if standard error is connected to a terminal.
993 Note that not all merge strategies may support progress
994 reporting.
995</p>
996</dd>
997<dt class="hdlist1">
Junio C Hamano1974bf22007-10-31 05:57:20998-m &lt;msg&gt;
Junio C Hamano1a4e8412005-12-27 08:17:23999</dt>
1000<dd>
1001<p>
Junio C Hamanoc0e55e72009-10-10 00:56:291002 Set the commit message to be used for the merge commit (in
Junio C Hamanof5de4cf2010-06-19 00:33:171003 case one is created).
Junio C Hamano1a4e8412005-12-27 08:17:231004</p>
Junio C Hamano9d971152012-12-19 00:43:111005<div class="paragraph"><p>If <code>--log</code> is specified, a shortlog of the commits being merged
Junio C Hamano68cf15a2010-11-06 01:01:591006will be appended to the specified message.</p></div>
1007<div class="paragraph"><p>The <em>git fmt-merge-msg</em> command can be
1008used to give a good default for automated <em>git merge</em>
1009invocations.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:231010</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591011<dt class="hdlist1">
Junio C Hamano19107ef2010-01-19 06:20:591012--rerere-autoupdate
1013</dt>
Junio C Hamano68cf15a2010-11-06 01:01:591014<dt class="hdlist1">
Junio C Hamano19107ef2010-01-19 06:20:591015--no-rerere-autoupdate
1016</dt>
1017<dd>
1018<p>
1019 Allow the rerere mechanism to update the index with the
1020 result of auto-conflict resolution if possible.
1021</p>
1022</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591023<dt class="hdlist1">
Junio C Hamano788eeba2010-12-08 22:50:431024--abort
1025</dt>
1026<dd>
1027<p>
1028 Abort the current conflict resolution process, and
1029 try to reconstruct the pre-merge state.
1030</p>
1031<div class="paragraph"><p>If there were uncommitted worktree changes present when the merge
1032started, <em>git merge --abort</em> will in some cases be unable to
1033reconstruct these changes. It is therefore recommended to always
1034commit or stash your changes before running <em>git merge</em>.</p></div>
1035<div class="paragraph"><p><em>git merge --abort</em> is equivalent to <em>git reset --merge</em> when
Junio C Hamano9d971152012-12-19 00:43:111036<code>MERGE_HEAD</code> is present.</p></div>
Junio C Hamano788eeba2010-12-08 22:50:431037</dd>
1038<dt class="hdlist1">
Junio C Hamano1aa40d22010-01-21 17:46:431039&lt;commit&gt;&#8230;
Junio C Hamano1a4e8412005-12-27 08:17:231040</dt>
1041<dd>
1042<p>
Junio C Hamano1aa40d22010-01-21 17:46:431043 Commits, usually other branch heads, to merge into our branch.
Junio C Hamanoa03ac862011-04-02 04:32:291044 Specifying more than one commit will create a merge with
1045 more than two parents (affectionately called an Octopus merge).
Junio C Hamano1a4e8412005-12-27 08:17:231046</p>
Junio C Hamano9d971152012-12-19 00:43:111047<div class="paragraph"><p>If no commit is given from the command line, and if <code>merge.defaultToUpstream</code>
Junio C Hamanoa1295452012-11-13 22:32:041048configuration variable is set, merge the remote-tracking branches
Junio C Hamanoa03ac862011-04-02 04:32:291049that the current branch is configured to use as its upstream.
1050See also the configuration section of this manual page.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:231051</dd>
Junio C Hamanoba4b9282008-07-06 05:20:311052</dl></div>
Junio C Hamano1a4e8412005-12-27 08:17:231053</div>
Junio C Hamano9d971152012-12-19 00:43:111054</div>
1055<div class="sect1">
Junio C Hamanod0d892c2010-01-24 20:06:291056<h2 id="_pre_merge_checks">PRE-MERGE CHECKS</h2>
1057<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591058<div class="paragraph"><p>Before applying outside changes, you should get your own work in
Junio C Hamanod0d892c2010-01-24 20:06:291059good shape and committed locally, so it will not be clobbered if
Junio C Hamanoa28a9202012-06-21 07:08:231060there are conflicts. See also <a href="git-stash.html">git-stash(1)</a>.
Junio C Hamanod0d892c2010-01-24 20:06:291061<em>git pull</em> and <em>git merge</em> will stop without doing anything when
1062local uncommitted changes overlap with files that <em>git pull</em>/<em>git
1063merge</em> may need to update.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591064<div class="paragraph"><p>To avoid recording unrelated changes in the merge commit,
Junio C Hamanod0d892c2010-01-24 20:06:291065<em>git pull</em> and <em>git merge</em> will also abort if there are any changes
Junio C Hamano9d971152012-12-19 00:43:111066registered in the index relative to the <code>HEAD</code> commit. (One
Junio C Hamanod0d892c2010-01-24 20:06:291067exception is when the changed index entries are in the state that
1068would result from the merge already.)</p></div>
Junio C Hamano9d971152012-12-19 00:43:111069<div class="paragraph"><p>If all named commits are already ancestors of <code>HEAD</code>, <em>git merge</em>
Junio C Hamanod0d892c2010-01-24 20:06:291070will exit early with the message "Already up-to-date."</p></div>
1071</div>
Junio C Hamano9d971152012-12-19 00:43:111072</div>
1073<div class="sect1">
Junio C Hamanod0d892c2010-01-24 20:06:291074<h2 id="_fast_forward_merge">FAST-FORWARD MERGE</h2>
1075<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591076<div class="paragraph"><p>Often the current branch head is an ancestor of the named commit.
Junio C Hamanod0d892c2010-01-24 20:06:291077This is the most common case especially when invoked from <em>git
1078pull</em>: you are tracking an upstream repository, you have committed
1079no local changes, and now you want to update to a newer upstream
1080revision. In this case, a new commit is not needed to store the
Junio C Hamano9d971152012-12-19 00:43:111081combined history; instead, the <code>HEAD</code> (along with the index) is
Junio C Hamanod0d892c2010-01-24 20:06:291082updated to point at the named commit, without creating an extra
1083merge commit.</p></div>
Junio C Hamano9d971152012-12-19 00:43:111084<div class="paragraph"><p>This behavior can be suppressed with the <code>--no-ff</code> option.</p></div>
Junio C Hamanod0d892c2010-01-24 20:06:291085</div>
Junio C Hamano9d971152012-12-19 00:43:111086</div>
1087<div class="sect1">
Junio C Hamanod0d892c2010-01-24 20:06:291088<h2 id="_true_merge">TRUE MERGE</h2>
1089<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591090<div class="paragraph"><p>Except in a fast-forward merge (see above), the branches to be
Junio C Hamanod0d892c2010-01-24 20:06:291091merged must be tied together by a merge commit that has both of them
1092as its parents.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591093<div class="paragraph"><p>A merged version reconciling the changes from all branches to be
Junio C Hamano9d971152012-12-19 00:43:111094merged is committed, and your <code>HEAD</code>, index, and working tree are
Junio C Hamanod0d892c2010-01-24 20:06:291095updated to it. It is possible to have modifications in the working
1096tree as long as they do not overlap; the update will preserve them.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591097<div class="paragraph"><p>When it is not obvious how to reconcile the changes, the following
Junio C Hamanod0d892c2010-01-24 20:06:291098happens:</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591099<div class="olist arabic"><ol class="arabic">
Junio C Hamanod0d892c2010-01-24 20:06:291100<li>
1101<p>
Junio C Hamano9d971152012-12-19 00:43:111102The <code>HEAD</code> pointer stays the same.
Junio C Hamanod0d892c2010-01-24 20:06:291103</p>
1104</li>
1105<li>
1106<p>
Junio C Hamano9d971152012-12-19 00:43:111107The <code>MERGE_HEAD</code> ref is set to point to the other branch head.
Junio C Hamanod0d892c2010-01-24 20:06:291108</p>
1109</li>
1110<li>
1111<p>
1112Paths that merged cleanly are updated both in the index file and
1113 in your working tree.
1114</p>
1115</li>
1116<li>
1117<p>
1118For conflicting paths, the index file records up to three
1119 versions: stage 1 stores the version from the common ancestor,
Junio C Hamano9d971152012-12-19 00:43:111120 stage 2 from <code>HEAD</code>, and stage 3 from <code>MERGE_HEAD</code> (you
1121 can inspect the stages with <code>git ls-files -u</code>). The working
Junio C Hamanod0d892c2010-01-24 20:06:291122 tree files contain the result of the "merge" program; i.e. 3-way
Junio C Hamano9d971152012-12-19 00:43:111123 merge results with familiar conflict markers <code>&lt;&lt;&lt;</code> <code>===</code> <code>&gt;&gt;&gt;</code>.
Junio C Hamanod0d892c2010-01-24 20:06:291124</p>
1125</li>
1126<li>
1127<p>
1128No other changes are made. In particular, the local
1129 modifications you had before you started merge will stay the
1130 same and the index entries for them stay as they were,
Junio C Hamano9d971152012-12-19 00:43:111131 i.e. matching <code>HEAD</code>.
Junio C Hamanod0d892c2010-01-24 20:06:291132</p>
1133</li>
1134</ol></div>
Junio C Hamano68cf15a2010-11-06 01:01:591135<div class="paragraph"><p>If you tried a merge which resulted in complex conflicts and
Junio C Hamano9d971152012-12-19 00:43:111136want to start over, you can recover with <code>git merge --abort</code>.</p></div>
Junio C Hamanod0d892c2010-01-24 20:06:291137</div>
Junio C Hamano9d971152012-12-19 00:43:111138</div>
1139<div class="sect1">
Junio C Hamanod0d892c2010-01-24 20:06:291140<h2 id="_how_conflicts_are_presented">HOW CONFLICTS ARE PRESENTED</h2>
1141<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591142<div class="paragraph"><p>During a merge, the working tree files are updated to reflect the result
1143of the merge. Among the changes made to the common ancestor&#8217;s version,
Junio C Hamanod0d892c2010-01-24 20:06:291144non-overlapping ones (that is, you changed an area of the file while the
1145other side left that area intact, or vice versa) are incorporated in the
1146final result verbatim. When both sides made changes to the same area,
Junio C Hamano076ffcc2013-02-06 05:13:211147however, Git cannot randomly pick one side over the other, and asks you to
Junio C Hamanod0d892c2010-01-24 20:06:291148resolve it by leaving what both sides did to that area.</p></div>
Junio C Hamano076ffcc2013-02-06 05:13:211149<div class="paragraph"><p>By default, Git uses the same style as the one used by the "merge" program
Junio C Hamanod0d892c2010-01-24 20:06:291150from the RCS suite to present such a conflicted hunk, like this:</p></div>
1151<div class="listingblock">
1152<div class="content">
Junio C Hamano9d971152012-12-19 00:43:111153<pre><code>Here are lines that are either unchanged from the common
Junio C Hamanod0d892c2010-01-24 20:06:291154ancestor, or cleanly resolved because only one side changed.
1155&lt;&lt;&lt;&lt;&lt;&lt;&lt; yours:sample.txt
1156Conflict resolution is hard;
1157let's go shopping.
1158=======
1159Git makes conflict resolution easy.
1160&gt;&gt;&gt;&gt;&gt;&gt;&gt; theirs:sample.txt
Junio C Hamano9d971152012-12-19 00:43:111161And here is another line that is cleanly resolved or unmodified.</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:291162</div></div>
Junio C Hamano68cf15a2010-11-06 01:01:591163<div class="paragraph"><p>The area where a pair of conflicting changes happened is marked with markers
Junio C Hamano9d971152012-12-19 00:43:111164<code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</code>, <code>=======</code>, and <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code>. The part before the <code>=======</code>
Junio C Hamanod0d892c2010-01-24 20:06:291165is typically your side, and the part afterwards is typically their side.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591166<div class="paragraph"><p>The default format does not show what the original said in the conflicting
Junio C Hamanod0d892c2010-01-24 20:06:291167area. You cannot tell how many lines are deleted and replaced with
Junio C Hamano68cf15a2010-11-06 01:01:591168Barbie&#8217;s remark on your side. The only thing you can tell is that your
1169side wants to say it is hard and you&#8217;d prefer to go shopping, while the
Junio C Hamanod0d892c2010-01-24 20:06:291170other side wants to claim it is easy.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591171<div class="paragraph"><p>An alternative style can be used by setting the "merge.conflictstyle"
Junio C Hamanod0d892c2010-01-24 20:06:291172configuration variable to "diff3". In "diff3" style, the above conflict
1173may look like this:</p></div>
1174<div class="listingblock">
1175<div class="content">
Junio C Hamano9d971152012-12-19 00:43:111176<pre><code>Here are lines that are either unchanged from the common
Junio C Hamanod0d892c2010-01-24 20:06:291177ancestor, or cleanly resolved because only one side changed.
1178&lt;&lt;&lt;&lt;&lt;&lt;&lt; yours:sample.txt
1179Conflict resolution is hard;
1180let's go shopping.
1181|||||||
1182Conflict resolution is hard.
1183=======
1184Git makes conflict resolution easy.
1185&gt;&gt;&gt;&gt;&gt;&gt;&gt; theirs:sample.txt
Junio C Hamano9d971152012-12-19 00:43:111186And here is another line that is cleanly resolved or unmodified.</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:291187</div></div>
Junio C Hamano9d971152012-12-19 00:43:111188<div class="paragraph"><p>In addition to the <code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</code>, <code>=======</code>, and <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code> markers, it uses
1189another <code>|||||||</code> marker that is followed by the original text. You can
Junio C Hamanod0d892c2010-01-24 20:06:291190tell that the original just stated a fact, and your side simply gave in to
1191that statement and gave up, while the other side tried to have a more
1192positive attitude. You can sometimes come up with a better resolution by
1193viewing the original.</p></div>
1194</div>
Junio C Hamano9d971152012-12-19 00:43:111195</div>
1196<div class="sect1">
Junio C Hamanod0d892c2010-01-24 20:06:291197<h2 id="_how_to_resolve_conflicts">HOW TO RESOLVE CONFLICTS</h2>
1198<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591199<div class="paragraph"><p>After seeing a conflict, you can do two things:</p></div>
1200<div class="ulist"><ul>
Junio C Hamanod0d892c2010-01-24 20:06:291201<li>
1202<p>
1203Decide not to merge. The only clean-ups you need are to reset
Junio C Hamano9d971152012-12-19 00:43:111204 the index file to the <code>HEAD</code> commit to reverse 2. and to clean
1205 up working tree changes made by 2. and 3.; <code>git merge --abort</code>
Junio C Hamano788eeba2010-12-08 22:50:431206 can be used for this.
Junio C Hamanod0d892c2010-01-24 20:06:291207</p>
1208</li>
1209<li>
1210<p>
1211Resolve the conflicts. Git will mark the conflicts in
1212 the working tree. Edit the files into shape and
1213 <em>git add</em> them to the index. Use <em>git commit</em> to seal the deal.
1214</p>
1215</li>
1216</ul></div>
Junio C Hamano68cf15a2010-11-06 01:01:591217<div class="paragraph"><p>You can work through the conflict with a number of tools:</p></div>
1218<div class="ulist"><ul>
Junio C Hamanod0d892c2010-01-24 20:06:291219<li>
1220<p>
Junio C Hamano9d971152012-12-19 00:43:111221Use a mergetool. <code>git mergetool</code> to launch a graphical
Junio C Hamanod0d892c2010-01-24 20:06:291222 mergetool which will work you through the merge.
1223</p>
1224</li>
1225<li>
1226<p>
Junio C Hamano9d971152012-12-19 00:43:111227Look at the diffs. <code>git diff</code> will show a three-way diff,
1228 highlighting changes from both the <code>HEAD</code> and <code>MERGE_HEAD</code>
Junio C Hamanod0d892c2010-01-24 20:06:291229 versions.
1230</p>
1231</li>
1232<li>
1233<p>
Junio C Hamano9d971152012-12-19 00:43:111234Look at the diffs from each branch. <code>git log --merge -p &lt;path&gt;</code>
1235 will show diffs first for the <code>HEAD</code> version and then the
1236 <code>MERGE_HEAD</code> version.
Junio C Hamanod0d892c2010-01-24 20:06:291237</p>
1238</li>
1239<li>
1240<p>
Junio C Hamano9d971152012-12-19 00:43:111241Look at the originals. <code>git show :1:filename</code> shows the
1242 common ancestor, <code>git show :2:filename</code> shows the <code>HEAD</code>
1243 version, and <code>git show :3:filename</code> shows the <code>MERGE_HEAD</code>
Junio C Hamanod0d892c2010-01-24 20:06:291244 version.
1245</p>
1246</li>
1247</ul></div>
1248</div>
Junio C Hamano9d971152012-12-19 00:43:111249</div>
1250<div class="sect1">
Junio C Hamanod0d892c2010-01-24 20:06:291251<h2 id="_examples">EXAMPLES</h2>
1252<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591253<div class="ulist"><ul>
Junio C Hamanod0d892c2010-01-24 20:06:291254<li>
1255<p>
Junio C Hamano9d971152012-12-19 00:43:111256Merge branches <code>fixes</code> and <code>enhancements</code> on top of
Junio C Hamanod0d892c2010-01-24 20:06:291257 the current branch, making an octopus merge:
1258</p>
1259<div class="listingblock">
1260<div class="content">
Junio C Hamano9d971152012-12-19 00:43:111261<pre><code>$ git merge fixes enhancements</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:291262</div></div>
1263</li>
1264<li>
1265<p>
Junio C Hamano9d971152012-12-19 00:43:111266Merge branch <code>obsolete</code> into the current branch, using <code>ours</code>
Junio C Hamanod0d892c2010-01-24 20:06:291267 merge strategy:
1268</p>
1269<div class="listingblock">
1270<div class="content">
Junio C Hamano9d971152012-12-19 00:43:111271<pre><code>$ git merge -s ours obsolete</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:291272</div></div>
1273</li>
1274<li>
1275<p>
Junio C Hamano9d971152012-12-19 00:43:111276Merge branch <code>maint</code> into the current branch, but do not make
Junio C Hamanod0d892c2010-01-24 20:06:291277 a new commit automatically:
1278</p>
1279<div class="listingblock">
1280<div class="content">
Junio C Hamano9d971152012-12-19 00:43:111281<pre><code>$ git merge --no-commit maint</code></pre>
Junio C Hamanod0d892c2010-01-24 20:06:291282</div></div>
Junio C Hamano68cf15a2010-11-06 01:01:591283<div class="paragraph"><p>This can be used when you want to include further changes to the
Junio C Hamanod0d892c2010-01-24 20:06:291284merge, or want to write your own merge commit message.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591285<div class="paragraph"><p>You should refrain from abusing this option to sneak substantial
Junio C Hamanod0d892c2010-01-24 20:06:291286changes into a merge commit. Small fixups like bumping
1287release/version name would be acceptable.</p></div>
1288</li>
1289</ul></div>
1290</div>
Junio C Hamano9d971152012-12-19 00:43:111291</div>
1292<div class="sect1">
Junio C Hamanoba4b9282008-07-06 05:20:311293<h2 id="_merge_strategies">MERGE STRATEGIES</h2>
Junio C Hamano1a4e8412005-12-27 08:17:231294<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591295<div class="paragraph"><p>The merge mechanism (<em>git-merge</em> and <em>git-pull</em> commands) allows the
Junio C Hamano9d971152012-12-19 00:43:111296backend <em>merge strategies</em> to be chosen with <code>-s</code> option. Some strategies
1297can also take their own options, which can be passed by giving <code>-X&lt;option&gt;</code>
Junio C Hamano1aa40d22010-01-21 17:46:431298arguments to <em>git-merge</em> and/or <em>git-pull</em>.</p></div>
Junio C Hamano68cf15a2010-11-06 01:01:591299<div class="dlist"><dl>
1300<dt class="hdlist1">
Junio C Hamano1a4e8412005-12-27 08:17:231301resolve
1302</dt>
1303<dd>
1304<p>
1305 This can only resolve two heads (i.e. the current branch
Junio C Hamano1de75722009-03-26 08:39:381306 and another branch you pulled from) using a 3-way merge
Junio C Hamano1a4e8412005-12-27 08:17:231307 algorithm. It tries to carefully detect criss-cross
1308 merge ambiguities and is considered generally safe and
1309 fast.
1310</p>
1311</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591312<dt class="hdlist1">
Junio C Hamano1a4e8412005-12-27 08:17:231313recursive
1314</dt>
1315<dd>
1316<p>
Junio C Hamano1de75722009-03-26 08:39:381317 This can only resolve two heads using a 3-way merge
1318 algorithm. When there is more than one common
1319 ancestor that can be used for 3-way merge, it creates a
Junio C Hamano1a4e8412005-12-27 08:17:231320 merged tree of the common ancestors and uses that as
1321 the reference tree for the 3-way merge. This has been
1322 reported to result in fewer merge conflicts without
1323 causing mis-merges by tests done on actual merge commits
1324 taken from Linux 2.6 kernel development history.
1325 Additionally this can detect and handle merges involving
1326 renames. This is the default merge strategy when
1327 pulling or merging one branch.
1328</p>
Junio C Hamano68cf15a2010-11-06 01:01:591329<div class="paragraph"><p>The <em>recursive</em> strategy can take the following options:</p></div>
1330<div class="dlist"><dl>
1331<dt class="hdlist1">
Junio C Hamano1aa40d22010-01-21 17:46:431332ours
1333</dt>
1334<dd>
1335<p>
1336 This option forces conflicting hunks to be auto-resolved cleanly by
1337 favoring <em>our</em> version. Changes from the other tree that do not
1338 conflict with our side are reflected to the merge result.
Junio C Hamanoa3cfb762012-09-15 05:32:141339 For a binary file, the entire contents are taken from our side.
Junio C Hamano1aa40d22010-01-21 17:46:431340</p>
Junio C Hamano68cf15a2010-11-06 01:01:591341<div class="paragraph"><p>This should not be confused with the <em>ours</em> merge strategy, which does not
Junio C Hamano1aa40d22010-01-21 17:46:431342even look at what the other tree contains at all. It discards everything
1343the other tree did, declaring <em>our</em> history contains all that happened in it.</p></div>
1344</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591345<dt class="hdlist1">
Junio C Hamano1aa40d22010-01-21 17:46:431346theirs
1347</dt>
1348<dd>
1349<p>
Junio C Hamanoa3cfb762012-09-15 05:32:141350 This is the opposite of <em>ours</em>.
Junio C Hamano1aa40d22010-01-21 17:46:431351</p>
1352</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591353<dt class="hdlist1">
Junio C Hamano39c7a692010-10-27 06:08:541354patience
1355</dt>
1356<dd>
1357<p>
1358 With this option, <em>merge-recursive</em> spends a little extra time
1359 to avoid mismerges that sometimes occur due to unimportant
1360 matching lines (e.g., braces from distinct functions). Use
1361 this when the branches to be merged have diverged wildly.
Junio C Hamano9d971152012-12-19 00:43:111362 See also <a href="git-diff.html">git-diff(1)</a> <code>--patience</code>.
Junio C Hamano39c7a692010-10-27 06:08:541363</p>
1364</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591365<dt class="hdlist1">
Junio C Hamano39c7a692010-10-27 06:08:541366ignore-space-change
1367</dt>
Junio C Hamano68cf15a2010-11-06 01:01:591368<dt class="hdlist1">
Junio C Hamano39c7a692010-10-27 06:08:541369ignore-all-space
1370</dt>
Junio C Hamano68cf15a2010-11-06 01:01:591371<dt class="hdlist1">
Junio C Hamano39c7a692010-10-27 06:08:541372ignore-space-at-eol
1373</dt>
1374<dd>
1375<p>
1376 Treats lines with the indicated type of whitespace change as
1377 unchanged for the sake of a three-way merge. Whitespace
1378 changes mixed with other changes to a line are not ignored.
Junio C Hamano9d971152012-12-19 00:43:111379 See also <a href="git-diff.html">git-diff(1)</a> <code>-b</code>, <code>-w</code>, and
1380 <code>--ignore-space-at-eol</code>.
Junio C Hamano39c7a692010-10-27 06:08:541381</p>
Junio C Hamano68cf15a2010-11-06 01:01:591382<div class="ulist"><ul>
Junio C Hamano39c7a692010-10-27 06:08:541383<li>
1384<p>
1385If <em>their</em> version only introduces whitespace changes to a line,
1386 <em>our</em> version is used;
1387</p>
1388</li>
1389<li>
1390<p>
1391If <em>our</em> version introduces whitespace changes but <em>their</em>
1392 version includes a substantial change, <em>their</em> version is used;
1393</p>
1394</li>
1395<li>
1396<p>
1397Otherwise, the merge proceeds in the usual way.
1398</p>
1399</li>
1400</ul></div>
1401</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591402<dt class="hdlist1">
Junio C Hamano2db3e752010-09-03 21:33:061403renormalize
1404</dt>
1405<dd>
1406<p>
1407 This runs a virtual check-out and check-in of all three stages
1408 of a file when resolving a three-way merge. This option is
1409 meant to be used when merging branches with different clean
1410 filters or end-of-line normalization rules. See "Merging
1411 branches with differing checkin/checkout attributes" in
Junio C Hamanoa28a9202012-06-21 07:08:231412 <a href="gitattributes.html">gitattributes(5)</a> for details.
Junio C Hamano2db3e752010-09-03 21:33:061413</p>
1414</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591415<dt class="hdlist1">
Junio C Hamano2db3e752010-09-03 21:33:061416no-renormalize
1417</dt>
1418<dd>
1419<p>
Junio C Hamano9d971152012-12-19 00:43:111420 Disables the <code>renormalize</code> option. This overrides the
1421 <code>merge.renormalize</code> configuration variable.
Junio C Hamano2db3e752010-09-03 21:33:061422</p>
1423</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591424<dt class="hdlist1">
Junio C Hamano39c7a692010-10-27 06:08:541425rename-threshold=&lt;n&gt;
1426</dt>
1427<dd>
1428<p>
1429 Controls the similarity threshold used for rename detection.
Junio C Hamano9d971152012-12-19 00:43:111430 See also <a href="git-diff.html">git-diff(1)</a> <code>-M</code>.
Junio C Hamano39c7a692010-10-27 06:08:541431</p>
1432</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591433<dt class="hdlist1">
Junio C Hamanod2179ef2010-10-22 04:12:171434subtree[=&lt;path&gt;]
Junio C Hamano1aa40d22010-01-21 17:46:431435</dt>
1436<dd>
1437<p>
1438 This option is a more advanced form of <em>subtree</em> strategy, where
1439 the strategy makes a guess on how two trees must be shifted to
1440 match with each other when merging. Instead, the specified path
1441 is prefixed (or stripped from the beginning) to make the shape of
1442 two trees to match.
1443</p>
1444</dd>
1445</dl></div>
Junio C Hamano1a4e8412005-12-27 08:17:231446</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591447<dt class="hdlist1">
Junio C Hamano1a4e8412005-12-27 08:17:231448octopus
1449</dt>
1450<dd>
1451<p>
Junio C Hamano1de75722009-03-26 08:39:381452 This resolves cases with more than two heads, but refuses to do
1453 a complex merge that needs manual resolution. It is
Junio C Hamano1a4e8412005-12-27 08:17:231454 primarily meant to be used for bundling topic branch
1455 heads together. This is the default merge strategy when
Junio C Hamano1de75722009-03-26 08:39:381456 pulling or merging more than one branch.
Junio C Hamano1a4e8412005-12-27 08:17:231457</p>
1458</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591459<dt class="hdlist1">
Junio C Hamano1a4e8412005-12-27 08:17:231460ours
1461</dt>
1462<dd>
1463<p>
Junio C Hamanobf984de2009-11-23 06:11:191464 This resolves any number of heads, but the resulting tree of the
1465 merge is always that of the current branch head, effectively
1466 ignoring all changes from all other branches. It is meant to
Junio C Hamano1a4e8412005-12-27 08:17:231467 be used to supersede old development history of side
Junio C Hamano1aa40d22010-01-21 17:46:431468 branches. Note that this is different from the -Xours option to
1469 the <em>recursive</em> merge strategy.
Junio C Hamano1a4e8412005-12-27 08:17:231470</p>
1471</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591472<dt class="hdlist1">
Junio C Hamanoe6c92032008-03-19 09:24:341473subtree
1474</dt>
1475<dd>
1476<p>
1477 This is a modified recursive strategy. When merging trees A and
1478 B, if B corresponds to a subtree of A, B is first adjusted to
1479 match the tree structure of A, instead of reading the trees at
1480 the same level. This adjustment is also done to the common
1481 ancestor tree.
1482</p>
1483</dd>
Junio C Hamanoba4b9282008-07-06 05:20:311484</dl></div>
Junio C Hamano1a4e8412005-12-27 08:17:231485</div>
Junio C Hamano9d971152012-12-19 00:43:111486</div>
1487<div class="sect1">
Junio C Hamanoba4b9282008-07-06 05:20:311488<h2 id="_configuration">CONFIGURATION</h2>
Junio C Hamano1e6e0062007-07-13 05:33:251489<div class="sectionbody">
Junio C Hamano68cf15a2010-11-06 01:01:591490<div class="dlist"><dl>
1491<dt class="hdlist1">
Junio C Hamano4653c6f2008-11-26 22:50:201492merge.conflictstyle
Junio C Hamano1e6e0062007-07-13 05:33:251493</dt>
1494<dd>
1495<p>
Junio C Hamano4653c6f2008-11-26 22:50:201496 Specify the style in which conflicted hunks are written out to
1497 working tree files upon merge. The default is "merge", which
Junio C Hamano9d971152012-12-19 00:43:111498 shows a <code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</code> conflict marker, changes made by one side,
1499 a <code>=======</code> marker, changes made by the other side, and then
1500 a <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</code> marker. An alternate style, "diff3", adds a <code>|||||||</code>
1501 marker and the original text before the <code>=======</code> marker.
Junio C Hamano6d76d612008-05-09 05:46:081502</p>
1503</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591504<dt class="hdlist1">
Junio C Hamanoa03ac862011-04-02 04:32:291505merge.defaultToUpstream
1506</dt>
1507<dd>
1508<p>
1509 If merge is called without any commit argument, merge the upstream
1510 branches configured for the current branch by using their last
Junio C Hamanoa1295452012-11-13 22:32:041511 observed values stored in their remote-tracking branches.
Junio C Hamano9d971152012-12-19 00:43:111512 The values of the <code>branch.&lt;current branch&gt;.merge</code> that name the
1513 branches at the remote named by <code>branch.&lt;current branch&gt;.remote</code>
1514 are consulted, and then they are mapped via <code>remote.&lt;remote&gt;.fetch</code>
Junio C Hamanoa1295452012-11-13 22:32:041515 to their corresponding remote-tracking branches, and the tips of
Junio C Hamanoa03ac862011-04-02 04:32:291516 these tracking branches are merged.
1517</p>
1518</dd>
1519<dt class="hdlist1">
Junio C Hamano3d050d62011-05-17 06:43:341520merge.ff
1521</dt>
1522<dd>
1523<p>
Junio C Hamano076ffcc2013-02-06 05:13:211524 By default, Git does not create an extra merge commit when merging
Junio C Hamano3d050d62011-05-17 06:43:341525 a commit that is a descendant of the current commit. Instead, the
Junio C Hamano9d971152012-12-19 00:43:111526 tip of the current branch is fast-forwarded. When set to <code>false</code>,
Junio C Hamano076ffcc2013-02-06 05:13:211527 this variable tells Git to create an extra merge commit in such
Junio C Hamano9d971152012-12-19 00:43:111528 a case (equivalent to giving the <code>--no-ff</code> option from the command
1529 line). When set to <code>only</code>, only such fast-forward merges are
1530 allowed (equivalent to giving the <code>--ff-only</code> option from the
Junio C Hamano3d050d62011-05-17 06:43:341531 command line).
1532</p>
1533</dd>
1534<dt class="hdlist1">
Junio C Hamano6d76d612008-05-09 05:46:081535merge.log
1536</dt>
1537<dd>
1538<p>
Junio C Hamano3b4609d2010-09-30 00:04:341539 In addition to branch names, populate the log message with at
1540 most the specified number of one-line descriptions from the
1541 actual commits that are being merged. Defaults to false, and
Junio C Hamano7165bf72011-01-04 22:06:181542 true is a synonym for 20.
Junio C Hamano6d76d612008-05-09 05:46:081543</p>
1544</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591545<dt class="hdlist1">
Junio C Hamano2fbcd212008-05-14 22:26:071546merge.renameLimit
1547</dt>
1548<dd>
1549<p>
1550 The number of files to consider when performing rename detection
1551 during a merge; if not specified, defaults to the value of
1552 diff.renameLimit.
1553</p>
1554</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591555<dt class="hdlist1">
Junio C Hamano2db3e752010-09-03 21:33:061556merge.renormalize
1557</dt>
1558<dd>
1559<p>
Junio C Hamano076ffcc2013-02-06 05:13:211560 Tell Git that canonical representation of files in the
Junio C Hamano2db3e752010-09-03 21:33:061561 repository has changed over time (e.g. earlier commits record
1562 text files with CRLF line endings, but recent ones use LF line
Junio C Hamano076ffcc2013-02-06 05:13:211563 endings). In such a repository, Git can convert the data
Junio C Hamano2db3e752010-09-03 21:33:061564 recorded in commits to a canonical form before performing a
1565 merge to reduce unnecessary conflicts. For more information,
1566 see section "Merging branches with differing checkin/checkout
Junio C Hamanoa28a9202012-06-21 07:08:231567 attributes" in <a href="gitattributes.html">gitattributes(5)</a>.
Junio C Hamano2db3e752010-09-03 21:33:061568</p>
1569</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591570<dt class="hdlist1">
Junio C Hamano4653c6f2008-11-26 22:50:201571merge.stat
1572</dt>
1573<dd>
1574<p>
1575 Whether to print the diffstat between ORIG_HEAD and the merge result
1576 at the end of the merge. True by default.
1577</p>
1578</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591579<dt class="hdlist1">
Junio C Hamano6d76d612008-05-09 05:46:081580merge.tool
1581</dt>
1582<dd>
1583<p>
Junio C Hamanob5e079f2013-02-08 00:02:521584 Controls which merge tool is used by <a href="git-mergetool.html">git-mergetool(1)</a>.
1585 The list below shows the valid built-in values.
1586 Any other value is treated as a custom merge tool and requires
1587 that a corresponding mergetool.&lt;tool&gt;.cmd variable is defined.
Junio C Hamano1e6e0062007-07-13 05:33:251588</p>
Junio C Hamanob5e079f2013-02-08 00:02:521589<div class="ulist"><ul>
1590<li>
1591<p>
1592araxis
1593</p>
1594</li>
1595<li>
1596<p>
1597bc3
1598</p>
1599</li>
1600<li>
1601<p>
1602codecompare
1603</p>
1604</li>
1605<li>
1606<p>
1607deltawalker
1608</p>
1609</li>
1610<li>
1611<p>
1612diffuse
1613</p>
1614</li>
1615<li>
1616<p>
1617ecmerge
1618</p>
1619</li>
1620<li>
1621<p>
1622emerge
1623</p>
1624</li>
1625<li>
1626<p>
1627gvimdiff
1628</p>
1629</li>
1630<li>
1631<p>
1632gvimdiff2
1633</p>
1634</li>
1635<li>
1636<p>
1637kdiff3
1638</p>
1639</li>
1640<li>
1641<p>
1642meld
1643</p>
1644</li>
1645<li>
1646<p>
1647opendiff
1648</p>
1649</li>
1650<li>
1651<p>
1652p4merge
1653</p>
1654</li>
1655<li>
1656<p>
1657tkdiff
1658</p>
1659</li>
1660<li>
1661<p>
1662tortoisemerge
1663</p>
1664</li>
1665<li>
1666<p>
1667vimdiff
1668</p>
1669</li>
1670<li>
1671<p>
1672vimdiff2
1673</p>
1674</li>
1675<li>
1676<p>
1677xxdiff
1678</p>
1679</li>
1680</ul></div>
Junio C Hamano1e6e0062007-07-13 05:33:251681</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591682<dt class="hdlist1">
Junio C Hamano1e6e0062007-07-13 05:33:251683merge.verbosity
1684</dt>
1685<dd>
1686<p>
1687 Controls the amount of output shown by the recursive merge
1688 strategy. Level 0 outputs nothing except a final error
1689 message if conflicts were detected. Level 1 outputs only
1690 conflicts, 2 outputs conflicts and file changes. Level 5 and
1691 above outputs debugging information. The default is level 2.
Junio C Hamanoec87f522008-12-10 08:35:251692 Can be overridden by the <em>GIT_MERGE_VERBOSITY</em> environment variable.
Junio C Hamano1e6e0062007-07-13 05:33:251693</p>
1694</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591695<dt class="hdlist1">
Junio C Hamano6d76d612008-05-09 05:46:081696merge.&lt;driver&gt;.name
1697</dt>
1698<dd>
1699<p>
Junio C Hamanoec87f522008-12-10 08:35:251700 Defines a human-readable name for a custom low-level
Junio C Hamanoa28a9202012-06-21 07:08:231701 merge driver. See <a href="gitattributes.html">gitattributes(5)</a> for details.
Junio C Hamano6d76d612008-05-09 05:46:081702</p>
1703</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591704<dt class="hdlist1">
Junio C Hamano6d76d612008-05-09 05:46:081705merge.&lt;driver&gt;.driver
1706</dt>
1707<dd>
1708<p>
1709 Defines the command that implements a custom low-level
Junio C Hamanoa28a9202012-06-21 07:08:231710 merge driver. See <a href="gitattributes.html">gitattributes(5)</a> for details.
Junio C Hamano6d76d612008-05-09 05:46:081711</p>
1712</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591713<dt class="hdlist1">
Junio C Hamano6d76d612008-05-09 05:46:081714merge.&lt;driver&gt;.recursive
1715</dt>
1716<dd>
1717<p>
1718 Names a low-level merge driver to be used when
1719 performing an internal merge between common ancestors.
Junio C Hamanoa28a9202012-06-21 07:08:231720 See <a href="gitattributes.html">gitattributes(5)</a> for details.
Junio C Hamano6d76d612008-05-09 05:46:081721</p>
1722</dd>
Junio C Hamano68cf15a2010-11-06 01:01:591723<dt class="hdlist1">
Junio C Hamano1b50ce92007-10-03 12:05:531724branch.&lt;name&gt;.mergeoptions
1725</dt>
1726<dd>
1727<p>
1728 Sets default options for merging into branch &lt;name&gt;. The syntax and
Junio C Hamanoc0e55e72009-10-10 00:56:291729 supported options are the same as those of <em>git merge</em>, but option
1730 values containing whitespace characters are currently not supported.
Junio C Hamano1b50ce92007-10-03 12:05:531731</p>
1732</dd>
Junio C Hamanoba4b9282008-07-06 05:20:311733</dl></div>
Junio C Hamano1e6e0062007-07-13 05:33:251734</div>
Junio C Hamano9d971152012-12-19 00:43:111735</div>
1736<div class="sect1">
Junio C Hamanoba4b9282008-07-06 05:20:311737<h2 id="_see_also">SEE ALSO</h2>
Junio C Hamano1a4e8412005-12-27 08:17:231738<div class="sectionbody">
Junio C Hamanoa28a9202012-06-21 07:08:231739<div class="paragraph"><p><a href="git-fmt-merge-msg.html">git-fmt-merge-msg(1)</a>, <a href="git-pull.html">git-pull(1)</a>,
1740<a href="gitattributes.html">gitattributes(5)</a>,
1741<a href="git-reset.html">git-reset(1)</a>,
1742<a href="git-diff.html">git-diff(1)</a>, <a href="git-ls-files.html">git-ls-files(1)</a>,
1743<a href="git-add.html">git-add(1)</a>, <a href="git-rm.html">git-rm(1)</a>,
1744<a href="git-mergetool.html">git-mergetool(1)</a></p></div>
Junio C Hamanofa2ad882009-12-03 09:15:441745</div>
Junio C Hamano9d971152012-12-19 00:43:111746</div>
1747<div class="sect1">
Junio C Hamanofa2ad882009-12-03 09:15:441748<h2 id="_git">GIT</h2>
1749<div class="sectionbody">
Junio C Hamanoa28a9202012-06-21 07:08:231750<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
Junio C Hamanofa2ad882009-12-03 09:15:441751</div>
Junio C Hamano7bd050f2011-09-22 06:32:221752</div>
Junio C Hamano9d971152012-12-19 00:43:111753</div>
Junio C Hamano7bd050f2011-09-22 06:32:221754<div id="footnotes"><hr /></div>
Junio C Hamanofa2ad882009-12-03 09:15:441755<div id="footer">
1756<div id="footer-text">
Junio C Hamano076ffcc2013-02-06 05:13:211757Last updated 2013-02-05 21:07:26 PST
Junio C Hamanofa2ad882009-12-03 09:15:441758</div>
1759</div>
1760</body>
1761</html>