On 6/30/06, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote:
> > > > FYI I've been just battling this pipe for a couple of hours. The first > > steps were easy, but since I wanted to do it incrementally, the index has > > to be written every so often, and I seem not to be able to get that right. > > > Are you sure? Does something use the index between starting update-index > pipe and pclose? Yes, I am sure you have to write the cache before git-read-tree and git-write-tree ;-)
Indeed :) That's what pclose before git-write-tree is for (which was not the case as I published this optimization. Noticed it later. The last patch series has pclose before git-write-tree)
I must have done something severely wrong, though, since there are not too many places where they are called. The problem is more likely that the cache has to be _read_, and _before_ the first substituted call to git-update-index.
git-write-tree change index? - : 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