Heiko Voigt <hvoigt@xxxxxxxxxx> writes: > * The same holds true if we are switching between two trees > - * using read-tree -m A B. The index must match B after that. > + * using read-tree A B (without -m). The index must match B > + * after that. With given -m it can be a mix of the old index > + * and the read one. I think the justification of the original patch is completely bogus. Why not just drop the priming instead? Two-tree read-tree without -m does not make much sense but the result would look like an overlay of two trees, and is not likely to match either of the trees. -- 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