Hi all, I have a single workspace where executing merges occasionally leads to a left-over .git/index.lock file that prevents me from adding resolved conflicted files.
I'm running a sped-up integration/feature branch process, and the merges and conflict resolution are automated. But the index.lock thing is happening only in one repo of the three that are doing this. Any hints as to debugging this? (It is not a running background gc, the lock file is still around when there is nothing running any more, for hours.) Andreas -- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
