On Thursday, August 29, 2013 08:11:48 am Brad King wrote:
> fatal: Unable to create '....lock': File exists.
> If no other git process is currently running, this
> probably means a git process crashed in this repository
> earlier. Make sure no other git process is running and
> remove the file manually to continue.
I don't believe git currently tries to do any form of stale
lock recovery since it is racy and unreliable (both single
server or on a multi-server shared repo),
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