Junio C Hamano <gits...@pobox.com> writes: > But the point is that we do not want such an overhead in core, as > all of that is a useless waste of the cycle for a site that wants to > store the push certificate away outside of the repository itself.
By this I do not mean that cert blobs shouldn't become part of the in-repository record in _all_ installations that receive signed push certificates. An easy to reuse example shipped together with our source would be a good thing, and an easy to enable sample hook may even be better. It's just that I do not want to have any "solution" in the core part that everybody that wants to accept push certs must run, if the "solution" is not something we can endorse as the best current practice. And I do not yet see how anything along the lines of the patch that started this thread, or its extention by wrapping them with commit chain, would become that "best current practice". A sample hook, on the other hand, is simpler for people to experiment and we might even come up with an unversally useful best current prctice out of such an experiment, though.
