After Aborting a Rebase a different Commit is checked out
By ...@wolke7.net on November 25, 2011 08:17 (imported from Google Code)
What steps will reproduce the problem?
- Checkout a branch (e.g. "devel").
- Start rebase.
- When there is a conflict, abort the rebase with the abort button.
- Check the log.
What is the expected output? What do you see instead?
I would expect that branch "devel" is checked out as it was before starting the rebase process.
Instead, a different commit is checked out.
What version of the product are you using? On what operating system?
TortoiseGit 1.7.5, Git 18.104.22.168, Windows 7 64 bit.
Please provide any additional information below.
The problem only occurs when the rebase is aborted after starting it with the start button, not if the rebase dialog is closed directly after opening it.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information