"Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > I recently looked into issues where git merge-tree calls returned bogus data > (in one instance returning an empty tree for non-empty merge parents). By > the time I had a look at the corresponding repository, the issue was no > longer reproducible, but a closer look at the code combined with some manual > experimenting turned up the fact that missing tree objects aren't handled as > errors by git merge-tree. Looking good. Will replace. Thanks.
