Mike Hommey <m...@glandium.org> writes: > One of the first things parse_from does is unconditionally throw away > the tree for the given branch, and then the "from" tree is loaded. So > when the "from" commit is the current head of the branch, that make > fast-import do more work than necessary.
If it is very common that the next commit the input stream wants to create is often on top of the commit that was just created, and if it is very common that the input stream producer knows what the commit object name of the commit that was just created, then optimising for that case does not sound too bad. It really depends on two factors: - How likely is it that other people make the same mistake? - How bad the damage to parse_from() would be if we wanted to optimize for this case? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
