]> source.dussan.org Git - jgit.git/commit
RebaseCommand: detect and handle fast-forward properly 64/2364/3
authorMathias Kinzler <mathias.kinzler@sap.com>
Fri, 28 Jan 2011 14:03:02 +0000 (15:03 +0100)
committerMathias Kinzler <mathias.kinzler@sap.com>
Fri, 28 Jan 2011 14:03:02 +0000 (15:03 +0100)
commite8a1328d05aa55b7ace0d101e34b87422219c959
treea1c475e37f8456cc95752a1144b3589a824370e9
parentc544e96a4cd027a127bc6e6ad5277091b3c0da73
RebaseCommand: detect and handle fast-forward properly

This bug was hidden by an incomplete test: the current Rebase
implementation using the "git rebase -i" pattern does not work
correctly if fast-forwarding is involved. The reason for this is that
the log command does not return any commits in this case.
In addition, a check for already merged commits was introduced to
avoid spurious conflicts.

Change-Id: Ib9898fe0f982fa08e41f1dca9452c43de715fdb6
Signed-off-by: Mathias Kinzler <mathias.kinzler@sap.com>
org.eclipse.jgit.test/tst/org/eclipse/jgit/api/RebaseCommandTest.java
org.eclipse.jgit/src/org/eclipse/jgit/api/RebaseCommand.java
org.eclipse.jgit/src/org/eclipse/jgit/api/RebaseResult.java