Using git 1.7.10 on linux, I am trying to use git rebase -i on a branch of about 100 commits. I regularly, but not always come across this problem:
After I have indicated what changes I want to make ... for example. I just rewrite quite close to the top, git continues to work and shows the counter on the command line when applying commits: for example [17/100] ...
Usually it will be a fairly smooth operation, but often it stops in the middle, saying:
[detached HEAD 5e1a3c8] Commit message
Author: username
1 file changed, 14 inserts (+), 3 deletions (-)
fatal: cannot create '/ [path to repository] /. git / index.lock ': File exists.
Failed to apply 05e6b8ef Other commit message
When I run git rebase -continue, I get a message to commit the current commit and when I close the git rebase file continues, but it skips commit ... This is completely useless, so for now I just do it, but it’s a pain. ..
It may be possible to manually fix the problem with fixing the problem, and then continue, but I have not studied it yet.
Anyway, when I go and check index.lock does not exist. It may have existed at the moment git wanted to create it, but it definitely left before I could look at it using the file browser ...
ps : I cannot reproduce this if I do not have gitg open during reboot.
Any clues?
update: gitg 2.6, ,