2009/2/4 Matthieu Moy <Matthieu.Moy@xxxxxxx>: > Hi, > > I'm debugging a git assertion failure, which leaves a .git/index.lock > in the way. After running the failed command, git refuses to do > anything in this directory, complaining with: > > fatal: unable to create '.git/index.lock': File exists > > What I'm doing then is just "rm .git/index.lock". Is it safe to do it? > I guess I should just make sure there's no git process running, but is > there anything else to check? It should be safe, yes. Often it is even safe to remove .git/index itself, since you can restore it from the latest commit with 'git reset'. -- Mikael Magnusson -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
