>> I know you seem to be resistent to caches, but caches are **good** >> because they are local information, which by definition can be >> implementation-dependent; you can always generate the cache from the >> git repository if for some reason you need to extend it. [...] > > But it is not true that "you can always generate the cache from the > git repository" in this case; the patch-id that is to be saved is > _original_ patch-id of cherry-picked (or reverted) changeset. He's proposing storing the original patch id in the commit message, and caching the commit SHA->patch id association on the side. Paolo -- 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
