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
On 08/29/2013 11:32 AM, Martin Fick wrote:
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
Brad King brad.k...@kitware.com writes:
Nor should it in this case. I was saying that the front-end
needs to reject duplicate ref names from the stdin lines before
trying to lock the ref twice to avoid this message.
How about trying not to feed duplicates?
--
To unsubscribe from this list:
On 08/29/2013 12:21 PM, Junio C Hamano wrote:
Brad King brad.k...@kitware.com writes:
needs to reject duplicate ref names from the stdin lines before
trying to lock the ref twice to avoid this message.
How about trying not to feed duplicates?
Sure, perhaps it is simplest to push the
On 08/29/2013 02:07 PM, Junio C Hamano wrote:
I didn't mean to force the caller of new update-ref --stdin; the
new code you wrote for it is what feeds the input to update_refs()
function, and that is one place you can make sure you do not lock
yourself out.
Besides, if you get two updates
5 matches
Mail list logo
