On Mon, Apr 25, 2016 at 4:57 PM, Christian Couder <christian.couder@xxxxxxxxx> wrote: >> But why write so many times when nobody reads it? We only need to >> write before git-apply exits, > > You mean `git am` here I think. > >> either after successfully applying the >> whole series, or after it stops at conflicts, and maybe even at die() >> and SIGINT. Yes if git-apply segfaults, > > Here too. Yep it's git-am. I didn't read the series, I simply ran and misread the traces a bit. >> then the index update is lost, >> but in such a case, it's usually a good idea to restart fresh anyway. >> When you only write index once (or twice) it won't matter if >> split-index is used. > > Yeah I agree, but it would need further work, that can be done after > this series is merged. Sure. > And I am not sure if the potential gains on a typical rebase would be worth it. I didn't point it out, but in pathological cases where your patch series touches a lot of (or even every) files in the worktree, the gain from split-index lowers and could even disappear. I don't know how often that can happen in real life though. Also, if you start to use split-index often, please note that I haven't addressed the sharedindex.* pruning part (it's labeled "experimental" for a reason), you may have to un-split the index and rm $GIT_DIR/sharedindex.* manually from time to time to keep disk usage down. -- Duy -- To unsubscribe from this list: 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