Lines Matching full:rebase

265 Git-rebase, which allows us to clean up the commit history. So don't worry
771 After that we have the pleasure of doing an interactive ``rebase`` to clean up
780 tutorial and ``rebase`` it. You should try following along with your own
787     152d39fe7 (HEAD -> tutorial-rebase2, tutorial-rebase) tutorial: Start Submitting patch section
793     1e24a5fb5 (me/tutorial-rebase) fixup! tutorial
806 ``rebase`` and submitted a patch for review, so my original branch was just called
821     $ git rebase -i 5ca627b78\^
824 This begins an interactive ``rebase`` where commit ``5ca6427b78`` is the earliest
826 commit before this one. The interactive ``rebase`` command takes the last commit
857 file. If your ``rebase`` results in a merge conflict, then you have probably
860 Perhaps a better name for the interactive ``rebase`` command would be 'replay'. As
880     fixup 276edecab tutorial: Save changes before rebase
901 apart a commit. It is also possible using Git-rebase by marking a line with
918 type of ``rebase`` and then try rebuilding and running the test.
925     git rebase master
928 ``git rebase master``. You may find that after the rebase there is a merge
930 from a Makefile conflict which was caused by reordering commits in a ``rebase``).
944 want, stage the changes and continue the ``rebase`` with ``git rebase