Jeff King <peff@xxxxxxxx> writes: > There's also one other issue with generation numbers. How do you handle > grafts and object-replacement refs? If you graft history, your embedded > generation numbers will all be junk, and you can't trust them. By the way, I doubt your "invalidate and recompute generation cache when replacement changes" would really work when we consider object transfer (which is the whole point of deprecating graft with object replacement mechanism). For the purpose of connectivity check during object transfer, we deliberately _ignore_ the object replacements, so you would at least want to have an ability to show the generation number according to the "true" history recorded in commits (which can come from Linus's in-commit generation number once everybody migrates) and the generation number that takes grafts and replacements into account (for which we cannot depend on in-commit record). -- 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