Skip to content

Commit 1b6f411

Browse files
committed
Fix link to git release notes
1 parent 509dc98 commit 1b6f411

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2015-09-30-interactive-rebase-status.textile

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: "interactive rebase status"
44
category: intermediate
55
---
66

7-
With "git 2.6": https://github.com/git/git/blob/v2.6.0/Documentation/RelNotes/2.6.0.txt it's now easier than ever to keep track of your work during an interactive rebase.
7+
With "git 2.6":https://github.com/git/git/blob/v2.6.0/Documentation/RelNotes/2.6.0.txt it's now easier than ever to keep track of your work during an interactive rebase.
88

99
Previously, if you were rebasing interactively and had hit a conflict or stopped to reword a commit, git status would look like this:
1010

@@ -16,7 +16,7 @@ You are currently rebasing branch 'testbranch' on '0927cd6'.
1616
(fix conflicts and then run "git rebase --continue")
1717
</pre>
1818

19-
This only tells you what branch you started with and the target of your rebase. If you want to get information about which commit you'vestopped on, you need to turn to <pre>git log</pre>.
19+
This only tells you what branch you started with and the target of your rebase. If you want to get information about which commit you'vestopped on, you need to turn to "git log".
2020

2121
With the release of 2.6, git status now produces much more helpful output that *reminds you what you were doing*. It includes which rebase commands have finished already, and what's still left to do.
2222

0 commit comments

Comments
 (0)