On 10/6/05, Alex Riesen <raa.lkml@gmail.com> wrote: > > (a bit too intrusive). The patch fixes only update-index.c (the one I had > > problems with), there probably are other places were the situation is alike. > > of course there are "other places". Please, try the attached patch instead. > > For the record: the patch is supposed to help people with > "Unable to write new cachefile" kind of errors. Just as I thought the situation improved (by closing index.lock and unmapping index), it suddenly get worse: now I'm stuck on git-pull. git-merge-index (called at some point by git-pull) maps the index in, and starts git-merge-one-file for each (or the given) entry in the index. git-merge-one-file calls git-update-index, which wants to update the index. Which doesn't work, because it's locked by that piece of s$%^. The only working walkaround for me atm is unlinking indexfile before rename in commit_index_file :( - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Oct 07 22:44:49 2005
This archive was generated by hypermail 2.1.8 : 2005-10-07 22:44:53 EST