[BUG] Invalid rebase command leaves unclean status
- From
- ulrik <ulrik.sverdrup@gmail.com>
- Date
- Dec 19, 2007, 00:47 UTC
- Message-ID
- <a1b6cb1b0712181647v34822692t4a3d88f90cd7346@mail.gmail.com>
Hello git list
A bug in rebase -i: A typo in the command (for example in the branch name) still makes later invocations of rebase think a rebase is already in process.
I found this bug in master, and it was already reported to the mailing list under version 1.5.3.5, but there were no follow-ups to that mail. I'm using 1.5.3.7 and it is still present, and looking at the maint branch it does not seem to be mentioned in post-x.3.7 changes there. So I am now reporting this bug again. I'm sorry for not checking this in master, I'll have to ask someone on the list to do that.
Original email: http://marc.info/?l=git&m=119410951019002&w=2 Date: 2007-11-03 17:04:51 Message-ID: 200711031804.52259.elendil () planet ! nl
# A sample session: # Invoking rebase with a typo, there is no "muster" branch $ git rebase -i muster fatal: Needed a single revision Invalid base $ git rebase -i master Interactive rebase already started $ git rebase --abort fatal: Needed a single revision # Even though rebase --abort reports an error, rebase's internal state is now cleared
Regards, Ulrik Sverdrup