1 <?xml version=
"1.0" encoding=
"UTF-8"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
3 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
6 <meta http-equiv=
"Content-Type" content=
"application/xhtml+xml; charset=UTF-8" />
7 <meta name=
"generator" content=
"AsciiDoc 10.2.0" />
8 <title>How to rebase from an internal branch
</title>
9 <style type=
"text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
14 font-family: Georgia,serif;
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
22 #author, #revnumber, #revdate, #revremark,
24 font-family: Arial,Helvetica,sans-serif;
28 margin:
1em
5%
1em
5%;
33 text-decoration: underline;
49 h1, h2, h3, h4, h5, h6 {
57 border-bottom:
2px solid silver;
77 border:
1px solid silver;
88 ul
> li { color: #aaa; }
89 ul
> li
> * { color: black; }
91 .monospaced, code, pre {
92 font-family:
"Courier New", Courier, monospace;
99 white-space: pre-wrap;
109 #revnumber, #revdate, #revremark {
114 border-top:
2px solid silver;
120 padding-bottom:
0.5em;
124 padding-bottom:
0.5em;
129 margin-bottom:
1.5em;
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
135 margin-bottom:
1.5em;
137 div.admonitionblock {
139 margin-bottom:
2.0em;
144 div.content { /* Block element content. */
148 /* Block element titles. */
149 div.title, caption.title {
154 margin-bottom:
0.5em;
160 td div.title:first-child {
163 div.content div.title:first-child {
166 div.content + div.title {
170 div.sidebarblock
> div.content {
172 border:
1px solid #dddddd;
173 border-left:
4px solid #f0f0f0;
177 div.listingblock
> div.content {
178 border:
1px solid #dddddd;
179 border-left:
5px solid #f0f0f0;
184 div.quoteblock, div.verseblock {
188 border-left:
5px solid #f0f0f0;
192 div.quoteblock
> div.attribution {
197 div.verseblock
> pre.content {
198 font-family: inherit;
201 div.verseblock
> div.attribution {
205 /* DEPRECATED: Pre version
8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
210 div.admonitionblock .icon {
214 text-decoration: underline;
216 padding-right:
0.5em;
218 div.admonitionblock td.content {
220 border-left:
3px solid #dddddd;
223 div.exampleblock
> div.content {
224 border-left:
3px solid #dddddd;
228 div.imageblock div.content { padding-left:
0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
234 margin-bottom:
0.8em;
247 list-style-position: outside;
250 list-style-type: decimal;
253 list-style-type: lower-alpha;
256 list-style-type: upper-alpha;
259 list-style-type: lower-roman;
262 list-style-type: upper-roman;
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
269 margin-bottom:
0.1em;
281 margin-bottom:
0.8em;
284 padding-bottom:
15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
292 padding-right:
0.8em;
298 div.hdlist.compact tr {
307 .footnote, .footnoteref {
311 span.footnote, span.footnoteref {
312 vertical-align: super;
316 margin:
20px
0 20px
0;
320 #footnotes div.footnote {
326 border-top:
1px solid silver;
335 padding-right:
0.5em;
336 padding-bottom:
0.3em;
344 #footer-badges { display: none; }
348 margin-bottom:
2.5em;
356 margin-bottom:
0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
376 span.aqua { color: aqua; }
377 span.black { color: black; }
378 span.blue { color: blue; }
379 span.fuchsia { color: fuchsia; }
380 span.gray { color: gray; }
381 span.green { color: green; }
382 span.lime { color: lime; }
383 span.maroon { color: maroon; }
384 span.navy { color: navy; }
385 span.olive { color: olive; }
386 span.purple { color: purple; }
387 span.red { color: red; }
388 span.silver { color: silver; }
389 span.teal { color: teal; }
390 span.white { color: white; }
391 span.yellow { color: yellow; }
393 span.aqua-background { background: aqua; }
394 span.black-background { background: black; }
395 span.blue-background { background: blue; }
396 span.fuchsia-background { background: fuchsia; }
397 span.gray-background { background: gray; }
398 span.green-background { background: green; }
399 span.lime-background { background: lime; }
400 span.maroon-background { background: maroon; }
401 span.navy-background { background: navy; }
402 span.olive-background { background: olive; }
403 span.purple-background { background: purple; }
404 span.red-background { background: red; }
405 span.silver-background { background: silver; }
406 span.teal-background { background: teal; }
407 span.white-background { background: white; }
408 span.yellow-background { background: yellow; }
410 span.big { font-size:
2em; }
411 span.small { font-size:
0.6em; }
413 span.underline { text-decoration: underline; }
414 span.overline { text-decoration: overline; }
415 span.line-through { text-decoration: line-through; }
417 div.unbreakable { page-break-inside: avoid; }
427 margin-bottom:
1.5em;
429 div.tableblock
> table {
430 border:
3px solid #
527bbd;
432 thead, p.table.header {
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock
> table[
frame=
"void"] {
443 div.tableblock
> table[
frame=
"hsides"] {
444 border-left-style: none;
445 border-right-style: none;
447 div.tableblock
> table[
frame=
"vsides"] {
448 border-top-style: none;
449 border-bottom-style: none;
460 margin-bottom:
1.5em;
462 thead, p.tableblock.header {
473 border-color: #
527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
480 border-color: #
527bbd;
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
491 table.tableblock.frame-none {
492 border-style: hidden;
495 th.tableblock.halign-left, td.tableblock.halign-left {
498 th.tableblock.halign-center, td.tableblock.halign-center {
501 th.tableblock.halign-right, td.tableblock.halign-right {
505 th.tableblock.valign-top, td.tableblock.valign-top {
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
523 padding-bottom:
0.5em;
524 border-top:
2px solid silver;
525 border-bottom:
2px solid silver;
530 body.manpage div.sectionbody {
535 body.manpage div#toc { display: none; }
540 <script type=
"text/javascript">
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September
2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
554 * Feel free to use this script under the terms of the GNU General Public
555 * License, as long as you do not remove or alter this notice.
558 /* modified by Troy D. Hanson, September
2006. License: GPL */
559 /* modified by Stuart Rackham,
2006,
2009. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType ==
3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
569 else if (i.firstChild != null)
575 function TocEntry(el, text, toclevel) {
578 this.toclevel = toclevel;
581 function tocEntries(el, toclevels) {
582 var result = new Array;
583 var re = new RegExp('[hH]([
1-'+(toclevels+
1)+'])');
584 // Function that scans the DOM tree for header elements (the DOM2
585 // nodeIterator API would be a better technique but not supported by all
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType ==
1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
591 if (mo && (i.getAttribute(
"class") || i.getAttribute(
"className")) !=
"float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[
1]-
1);
602 var toc = document.getElementById(
"toc");
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
610 for (i =
0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute(
"class")
614 && entry.getAttribute(
"class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
617 for (i =
0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
621 // Rebuild TOC entries.
622 var entries = tocEntries(document.getElementById(
"content"), toclevels);
623 for (var i =
0; i < entries.length; ++i) {
624 var entry = entries[i];
625 if (entry.element.id ==
"")
626 entry.element.id =
"_toc_" + i;
627 var a = document.createElement(
"a");
628 a.href =
"#" + entry.element.id;
629 a.appendChild(document.createTextNode(entry.text));
630 var div = document.createElement(
"div");
632 div.className =
"toclevel" + entry.toclevel;
633 toc.appendChild(div);
635 if (entries.length ==
0)
636 toc.parentNode.removeChild(toc);
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
645 * http://www.brandspankingnew.net/archive/
2005/
07/format_footnote.html
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
651 var noteholder = document.getElementById(
"footnotes");
655 var entriesToRemove = [];
656 for (i =
0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
658 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute(
"class") ==
"footnote")
659 entriesToRemove.push(entry);
661 for (i =
0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
665 // Rebuild footnote entries.
666 var cont = document.getElementById(
"content");
667 var spans = cont.getElementsByTagName(
"span");
670 for (i=
0; i
<spans.length; i++) {
671 if (spans[i].className ==
"footnote") {
673 var note = spans[i].getAttribute(
"data-note");
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[
1];
679 "[<a id='_footnoteref_" + n +
"' href='#_footnote_" + n +
680 "' title='View footnote' class='footnote'>" + n +
"</a>]";
681 spans[i].setAttribute(
"data-note", note);
683 noteholder.innerHTML +=
684 "<div class='footnote' id='_footnote_" + n +
"'>" +
685 "<a href='#_footnoteref_" + n +
"' title='Return to text'>" +
686 n +
"</a>. " + note +
"</div>";
687 var id =spans[i].getAttribute(
"id");
688 if (id != null) refs[
"#"+id] = n;
692 noteholder.parentNode.removeChild(noteholder);
694 // Process footnoterefs.
695 for (i=
0; i
<spans.length; i++) {
696 if (spans[i].className ==
"footnoteref") {
697 var href = spans[i].getElementsByTagName(
"a")[
0].getAttribute(
"href");
698 href = href.match(/#.*/)[
0]; // Because IE return full URL.
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n +
"</a>]";
708 install: function(toclevels) {
711 function reinstall() {
712 asciidoc.footnotes();
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
723 timerId = setInterval(reinstall,
500);
724 if (document.addEventListener)
725 document.addEventListener(
"DOMContentLoaded", reinstallAndRemoveTimer, false);
727 window.onload = reinstallAndRemoveTimer;
735 <body class=
"article">
737 <h1>How to rebase from an internal branch
</h1>
738 <span id=
"revdate">2024-
01-
29</span>
742 <div class=
"sectionbody">
743 <div class=
"listingblock">
744 <div class=
"content">
745 <pre><code>Petr Baudis
<pasky@suse.cz
> writes:
747 > Dear diary, on Sun, Aug
14,
2005 at
09:
57:
13AM CEST, I got a letter
748 > where Junio C Hamano
<junkio@cox.net
> told me that...
749 >> Linus Torvalds
<torvalds@osdl.org
> writes:
751 >> > Junio, maybe you want to talk about how you move patches from your
752 >> > "seen" branch to the real branches.
754 > Actually, wouldn't this be also precisely for what StGIT is intended to?
</code></pre>
756 <div class=
"paragraph"><p>Exactly my feeling. I was sort of waiting for Catalin to speak
757 up. With its basing philosophical ancestry on quilt, this is
758 the kind of task StGIT is designed to do.
</p></div>
759 <div class=
"paragraph"><p>I just have done a simpler one, this time using only the core
761 <div class=
"paragraph"><p>I had a handful of commits that were ahead of master in
<em>seen
</em>, and I
762 wanted to add some documentation bypassing my usual habit of
763 placing new things in
<em>seen
</em> first. At the beginning, the commit
764 ancestry graph looked like this:
</p></div>
765 <div class=
"literalblock">
766 <div class=
"content">
767 <pre><code> *
"seen" head
768 master --
> #
1 --
> #
2 --
> #
3</code></pre>
770 <div class=
"paragraph"><p>So I started from master, made a bunch of edits, and committed:
</p></div>
771 <div class=
"literalblock">
772 <div class=
"content">
773 <pre><code>$ git checkout master
774 $ cd Documentation; ed git.txt ...
775 $ cd ..; git add Documentation/*.txt
776 $ git commit -s
</code></pre>
778 <div class=
"paragraph"><p>After the commit, the ancestry graph would look like this:
</p></div>
779 <div class=
"literalblock">
780 <div class=
"content">
781 <pre><code> *
"seen" head
782 master^ --
> #
1 --
> #
2 --
> #
3
784 \---
> master
</code></pre>
786 <div class=
"paragraph"><p>The old master is now master^ (the first parent of the master).
787 The new master commit holds my documentation updates.
</p></div>
788 <div class=
"paragraph"><p>Now I have to deal with
"seen" branch.
</p></div>
789 <div class=
"paragraph"><p>This is the kind of situation I used to have all the time when
790 Linus was the maintainer and I was a contributor, when you look
791 at
"master" branch being the
"maintainer" branch, and
"seen"
792 branch being the
"contributor" branch. Your work started at the
793 tip of the
"maintainer" branch some time ago, you made a lot of
794 progress in the meantime, and now the maintainer branch has some
795 other commits you do not have yet. And
"git rebase" was written
796 with the explicit purpose of helping to maintain branches like
797 "seen". You
<em>could
</em> merge master to
<em>seen
</em> and keep going, but if you
798 eventually want to cherrypick and merge some but not necessarily
799 all changes back to the master branch, it often makes later
800 operations for
<em>you
</em> easier if you rebase (i.e. carry forward
801 your changes)
"seen" rather than merge. So I ran
"git rebase":
</p></div>
802 <div class=
"literalblock">
803 <div class=
"content">
804 <pre><code>$ git checkout seen
805 $ git rebase master seen
</code></pre>
807 <div class=
"paragraph"><p>What this does is to pick all the commits since the current
808 branch (note that I now am on
"seen" branch) forked from the
809 master branch, and forward port these changes.
</p></div>
810 <div class=
"literalblock">
811 <div class=
"content">
812 <pre><code>master^ --
> #
1 --
> #
2 --
> #
3
814 \---
> master --
> #
1' --
> #
2' --
> #
3'
</code></pre>
816 <div class=
"paragraph"><p>The diff between master^ and #
1 is applied to master and
817 committed to create #
1' commit with the commit information (log,
818 author and date) taken from commit #
1. On top of that #
2' and #
3'
819 commits are made similarly out of #
2 and #
3 commits.
</p></div>
820 <div class=
"paragraph"><p>Old #
3 is not recorded in any of the .git/refs/heads/ file
821 anymore, so after doing this you will have dangling commit if
822 you ran fsck-cache, which is normal. After testing
"seen", you
823 can run
"git prune" to get rid of those original three commits.
</p></div>
824 <div class=
"paragraph"><p>While I am talking about
"git rebase", I should talk about how
825 to do cherrypicking using only the core Git tools.
</p></div>
826 <div class=
"paragraph"><p>Let
’s go back to the earlier picture, with different labels.
</p></div>
827 <div class=
"paragraph"><p>You, as an individual developer, cloned upstream repository and
828 made a couple of commits on top of it.
</p></div>
829 <div class=
"literalblock">
830 <div class=
"content">
831 <pre><code> *your
"master" head
832 upstream --
> #
1 --
> #
2 --
> #
3</code></pre>
834 <div class=
"paragraph"><p>You would want changes #
2 and #
3 incorporated in the upstream,
835 while you feel that #
1 may need further improvements. So you
836 prepare #
2 and #
3 for e-mail submission.
</p></div>
837 <div class=
"literalblock">
838 <div class=
"content">
839 <pre><code>$ git format-patch master^^ master
</code></pre>
841 <div class=
"paragraph"><p>This creates two files,
0001-XXXX.patch and
0002-XXXX.patch. Send
842 them out
"To: " your project maintainer and
"Cc: " your mailing
843 list. You could use contributed script git-send-email if
844 your host has necessary perl modules for this, but your usual
845 MUA would do as long as it does not corrupt whitespaces in the
847 <div class=
"paragraph"><p>Then you would wait, and you find out that the upstream picked
848 up your changes, along with other changes.
</p></div>
849 <div class=
"literalblock">
850 <div class=
"content">
851 <pre><code> where *your
"master" head
852 upstream --
> #
1 --
> #
2 --
> #
3
854 to be \--
> #A --
> #
2' --
> #
3' --
> #B --
> #C
855 *upstream head
</code></pre>
857 <div class=
"paragraph"><p>The two commits #
2' and #
3' in the above picture record the same
858 changes your e-mail submission for #
2 and #
3 contained, but
859 probably with the new sign-off line added by the upstream
860 maintainer and definitely with different committer and ancestry
861 information, they are different objects from #
2 and #
3 commits.
</p></div>
862 <div class=
"paragraph"><p>You fetch from upstream, but not merge.
</p></div>
863 <div class=
"literalblock">
864 <div class=
"content">
865 <pre><code>$ git fetch upstream
</code></pre>
867 <div class=
"paragraph"><p>This leaves the updated upstream head in .git/FETCH_HEAD but
868 does not touch your .git/HEAD or .git/refs/heads/master.
869 You run
"git rebase" now.
</p></div>
870 <div class=
"literalblock">
871 <div class=
"content">
872 <pre><code>$ git rebase FETCH_HEAD master
</code></pre>
874 <div class=
"paragraph"><p>Earlier, I said that rebase applies all the commits from your
875 branch on top of the upstream head. Well, I lied.
"git rebase"
876 is a bit smarter than that and notices that #
2 and #
3 need not
877 be applied, so it only applies #
1. The commit ancestry graph
878 becomes something like this:
</p></div>
879 <div class=
"literalblock">
880 <div class=
"content">
881 <pre><code> where *your old
"master" head
882 upstream --
> #
1 --
> #
2 --
> #
3
883 used \ your new
"master" head*
884 to be \--
> #A --
> #
2' --
> #
3' --
> #B --
> #C --
> #
1'
888 <div class=
"paragraph"><p>Again,
"git prune" would discard the disused commits #
1-#
3 and
889 you continue on starting from the new
"master" head, which is
890 the #
1' commit.
</p></div>
891 <div class=
"paragraph"><p>-jc
</p></div>
895 <div id=
"footnotes"><hr /></div>
897 <div id=
"footer-text">
899 2024-
01-
29 16:
09:
48 PST